none
Are datatables,datasets, datareaders convenient for a web application? RRS feed

  • Question

  •  

    Hello to all there, thank you very much for reading this post and help me to understand this better.

    I am gonna build a web application that will be working all over the internet with tons of users interacting with it, till now i have just developed applications that use a browser into an intranet environment, they were dependant of a local server that managed a limited number of users so their requests werent a huge problem for the local server to deal with and thats why i always used datasets, datatables, datareaders, even storing some of this objects into session variables to avoid a deletion action from the server after the request was finished, now i have just read an article that remarks how this methodology is a big limitation for a webapplication that is gonna be working through the internet due to its high dependance of the web server memory availability, causing a big problem for the hardware support when the webapplication handles a lot of traffic.

    I would like you to help me to figure if this is a real issue, if it is ok to keep ussing datasets, datatables, dataviews, datarows, etc to store and manage the data, or if i should use another data access technology available on asp.net to make of my application an efficient, fast, and scalable one. if its possible with some theoric references too about which would be more convenient in this case.

    Thanks for your time reading this, your help will be really appreciated.

    Peace.



    Tuesday, April 1, 2008 4:05 PM

All replies

  • Session variables use a lot of RAM, and ViewState uses a lot of bandwidth.  You should try to minimize use of both.

    It's not a big deal to allocate a bunch of temporary objects (datatables, etc) that are discarded when page processing is complete.  The .NET Framework does a fairly good job of cleaning up temporary stuff.  Still, you should try to keep the total memory requirements down if you can for performance benefits.

    Also, consider that it might be cheaper to just buy a very fast server instead of you spending 6+ months tuning your app.  Time is money Smile

    -Ryan / Kardax
    Tuesday, April 1, 2008 7:35 PM
  •  

    Hi Ryan, thank you very much for your opinion about this matter, i was worried about a pair of session variables storing a dataset or a datatable for a longer period on certain type of requests for what i first thought about a certain part of the site functionality, so after your recomendation i guess this wouldn't kill the server if i end up implementing on this way and ussing the ado.net data objects without session variables in shorter requests as well, Smile, besides that i am planning to use caching too. This author really confused me.

     

    Thanks for your time and your help any further suggestions from you or more friendly programmers will be great as well. 

     

    Best Regards.

     

    Choro.

     

     

     

     

     

     

     

     

    Tuesday, April 1, 2008 9:25 PM