locked
state management RRS feed

  • Question

  • User2096643634 posted

    Hello everyone,

                 I am to develop a web application which will be having around 500-600 concurrent users. Please let me know which state management technique should I use so that my applicaiton is scalable. At present, I use in-proc way of session management. Am using VS2008 and .net framework3.5.

    Thanks in advance...:)

    Thursday, November 24, 2011 5:17 AM

Answers

  • User2117486576 posted

    Here is some info about the sessionstate modes available:

    http://msdn.microsoft.com/en-us/library/ms178586.aspx

    The number of concurrent users is important but you also need to know the server resources, server configuration (web garder, etc.) and  what kind and how much data you are storing in Session.  Generally, very large amounts or large entities stored in Session are better using SqlServer mode, less you would probably want to use StateServer mode.  You also need to evaluate the performance hit each mode involves; SqlServer mode is or can be slow, InProc is probably the fastest.

     

    • Marked as answer by Anonymous Thursday, October 7, 2021 12:00 AM
    Thursday, November 24, 2011 7:59 AM

All replies

  • User-472055486 posted

    If the data securable you shoud use session

    other wise you can use cookies

    Thursday, November 24, 2011 7:21 AM
  • User2117486576 posted

    Here is some info about the sessionstate modes available:

    http://msdn.microsoft.com/en-us/library/ms178586.aspx

    The number of concurrent users is important but you also need to know the server resources, server configuration (web garder, etc.) and  what kind and how much data you are storing in Session.  Generally, very large amounts or large entities stored in Session are better using SqlServer mode, less you would probably want to use StateServer mode.  You also need to evaluate the performance hit each mode involves; SqlServer mode is or can be slow, InProc is probably the fastest.

     

    • Marked as answer by Anonymous Thursday, October 7, 2021 12:00 AM
    Thursday, November 24, 2011 7:59 AM
  • User2096643634 posted

    I am just storing the username in the session and it is not a web garden scenario.Please clarify wht do you mean by server resources. My server has windows XP SP3 and there is 1 application hosted by this server. RAM is 2 GB. But I was just wondering will it cause performance issue if my website is accessed by 500-600 users at a given point of time. I hope my system will not crash or IIS is not recycled coz in that case sessions will be lost.

    Thank you.

    Friday, November 25, 2011 12:44 AM
  • User2117486576 posted

    Server resources would include the physical RAM, processor, permamnant storage, etc.  From your description it would seem that InProc would be fine unless you are worried about app pool recycles, in which case use stateServer mode.

     

    As a note, you do not need to store the username in Session.  If you are using the standard authentication provider, then the username is available from any page as User.Identity.Name:

    http://msdn.microsoft.com/en-us/library/system.web.httpcontext.user.aspx

    Friday, November 25, 2011 7:37 AM