performance difference

Results 1 to 2 of 2

Thread: performance difference

  1. #1
    Join Date
    Dec 1969

    Default performance difference

    Are there any performance differences between the following<BR><BR>&#060;input type="text" id="name" size="10" runat="server"&#062;<BR>&#060;asp:textbox id="name" size="10" runat="server" /&#062;<BR><BR>i am creating a site which contains 3 pages and each page contains 10 textboxes. imagine everything runat=server...<BR><BR>i really need to know whether there is a real performance difference using htmlcontrols on server or webform textboxes on server.<BR><BR>thanks<BR>dotnetlover.

  2. #2
    Join Date
    Dec 1969

    Default RE: performance difference

    Hehe the money spent in extra development time you could probably just buy some more ram for the machine. If the machines got ram everything is good. <BR><BR>Theres a trade off. The controls do take up a little bit more memory. But... the execution is faster. And.. because of the way its designed.. The larger the application is the more efficient it will become... Its harder to write apps in normal asp. alot of the times due to bad design of code you&#039;ll end up wasting more memory anyways. For instance.. the recordset.. Creates locks on the sql server and generally is not an efficient way to access data ( relatively speaking to ). In your defenitely going to have a faster db performance.. Also... has an awesome garbage collector. So all objects created are destroyed properly.. For instance your textbox&#039;s. They dont sit there in memory for as long as your client is on the website. The information about the textbox is put in the viewstate. So its only put into memory when a postback occurs. And since the execution time is faster the memory is freed faster and efficiently. See thats the thing I think we fail to realize.. whats the point of saving memory if its going to sit in memory longer. Even if we have to use more memory to speed up the process then that memory will be available for other clients.. quicker. In traditional asp everything is so linear that there usually is alot of extra processing involved.. Because you have to handle the form processing yourself. Because is event driven.. Less code needs to be executed to perform specific tasks within your page. This is just the tip of the iceburg the list goes on and on.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts