Home/ Questions/Q 8246973
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-06-07T22:41:11+00:00

I am working on a page that has a dynamically generated markup. And as

  • 0

I am working on a page that has a dynamically generated markup. And as such, I have no idea what fields are available on the form. So instead of creating a view model, the POST method uses the FormCollection. Once the POST is received, the program runs quickly.

My problem: Clicking SUBMIT on the form will take about 10 – 15 seconds to hit a breakpoint on the first line of the POST action in the controller. In my scenario, there are 800 input fields on the form. Does it really take this long to create the FormCollection for only 800 fields? Are there any ways to streamline the process or improve the response time?

EDIT:

The IE profiler indicates the majority of time is spent in the JQuery CSS selector. If I remove all CSS, the page works very quickly. Why is the CSS selector running prior to posting back to the server? Can I disable it?

EDIT 2:
The profiler is now showing time spend in JQuery 1.6.4.min.js, the function is ‘k’. I think that is just an internal varialble lookup. I have also found that removing the ‘size’ and ‘maxlength’ attributes from the input fields makes the page respond quickly (hooray)… except… I need those for client side validation. I’m still trying to find a way to improve the speed, or remove the attributes and retain some way to limit the input length of the fields on the client side.

Edit 3:
I’ve dug into the jquery-1.6.4.min.js and found function k. Per Edit 2, adding/removing the ‘maxlength’ and ‘size’ attributes makes all the difference (33K ms instead of 3k ms). However, function K should not do much… as those are not nodetype===1 and the first IF should fail, returning out of the function on the next line.

function k(a,c,d)
    {
        if(d===b&&a.nodeType===1)
        {
            var e="data-"+c.replace(j,"-$1").toLowerCase();
            d=a.getAttribute(e);
            if(typeof d=="string")
            {
                try
                {
                    d=d==="true"?!0:d==="false"?!1:d==="null"?null:f.isNaN(d)?i.test(d)?f.parseJSON(d):d:parseFloat(d)
                }
                catch(g){}
                f.data(a,c,d)
            }
            else 
                d=b
        }
        return d
    }
Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    From comments with Mystere Man, it turns out somehow the client side was validating, this link solved the issue: http://forums.asp.net/t/1523883.aspx/1/10?Disabling+client+side+validation+on+submit+button+

    Basically, I disabled the validation on the submit button. This allows the ‘maxlength’ and ‘size’ attributes to work when the user types, but prevents any client side validation on the POST. This behavior seems fine, as the server will validate again as the input is processed. The average time for the POST changed from 33 seconds to 2 seconds.

    Also here: Disable client-side validation in MVC 3 "cancel" submit button

    • 0