asp.net session state service limitation?

  • Thread starter Thread starter Billy Zhang
  • Start date Start date
B

Billy Zhang

Hi All,

I am using asp.net session state service to store session.
The concurrent online user will be almost 2000.

Could asp.net session state service afford this?
Is there any limitation about asp.net session state service?

-Billy
 
it depends on the which session server you are using (inproc, state or sql).
if inproc or state server, then it will depend on the size of individual
session, and how much memory is allowed (32 vs 64 bit). if you use sqlserver
your only limit is dabase size.

it also depends on the cost of losing session data. inproc is lost on each
recycle (or idle timeout). appstate can lose due to too much memory pressure.


-- bruce (sqlwork.com)
 
I am using session state service not inproc.

bruce barker said:
it depends on the which session server you are using (inproc, state or sql).
if inproc or state server, then it will depend on the size of individual
session, and how much memory is allowed (32 vs 64 bit). if you use sqlserver
your only limit is dabase size.

it also depends on the cost of losing session data. inproc is lost on each
recycle (or idle timeout). appstate can lose due to too much memory pressure.


-- bruce (sqlwork.com)
Click to expand...
 
then you just have memory limits to worry about. also if the state
service fails or has to fail over to a backup machine you will lose all
session data. you will also need to keep the session fairly short (20-30
minutes instead of days or weeks).

-- bruce (sqlwork.com)
 
Thank you for your quick response!

-Billy

bruce barker said:
then you just have memory limits to worry about. also if the state
service fails or has to fail over to a backup machine you will lose all
session data. you will also need to keep the session fairly short (20-30
minutes instead of days or weeks).

-- bruce (sqlwork.com)
Click to expand...
 
Hi Billy,

As Bruce said, it depends on if you're using a 32-bit machine or a 64-bit
one. A 32-bit application running on Windows is only allowed to use 2GB
virtual memory by default. If the overall data size is larger than 2GB you
may see the out of memory error. If the memory pressure is low the ASP.NET
State Service definitely can afford 2000 concurrent sessions.

Regards,
Allen Chen
Microsoft Online Support

Delighting our customers is our #1 priority. We welcome your comments and
suggestions about how we can improve the support we provide to you. Please
feel free to let my manager know what you think of the level of service
provided. You can send feedback directly to my manager at:
(e-mail address removed).

==================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/en-us/subscriptions/aa948868.aspx#notifications.

Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
http://support.microsoft.com/select/default.aspx?target=assistance&ln=en-us.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.

--------------------
| Thread-Topic: asp.net session state service limitation?
| thread-index: Ackv+AMfkB35Iy0rR+uIq/sovcWYvw==
| X-WBNR-Posting-Host: 207.46.193.207
| From: =?Utf-8?B?QmlsbHkgWmhhbmc=?= <[email protected]>
| References: <[email protected]>
<[email protected]>
| Subject: RE: asp.net session state service limitation?
| Date: Thu, 16 Oct 2008 18:31:00 -0700
| Lines: 27
| Message-ID: <[email protected]>
| MIME-Version: 1.0
| Content-Type: text/plain;
| charset="Utf-8"
| Content-Transfer-Encoding: 7bit
| X-Newsreader: Microsoft CDO for Windows 2000
| Content-Class: urn:content-classes:message
| Importance: normal
| Priority: normal
| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.3119
| Newsgroups: microsoft.public.dotnet.framework.aspnet
| Path: TK2MSFTNGHUB02.phx.gbl
| Xref: TK2MSFTNGHUB02.phx.gbl
microsoft.public.dotnet.framework.aspnet:78040
| NNTP-Posting-Host: tk2msftibfm01.phx.gbl 10.40.244.149
| X-Tomcat-NG: microsoft.public.dotnet.framework.aspnet
|
| I am using session state service not inproc.
|
| "bruce barker" wrote:
|
| > it depends on the which session server you are using (inproc, state or
sql).
| > if inproc or state server, then it will depend on the size of
individual
| > session, and how much memory is allowed (32 vs 64 bit). if you use
sqlserver
| > your only limit is dabase size.
| >
| > it also depends on the cost of losing session data. inproc is lost on
each
| > recycle (or idle timeout). appstate can lose due to too much memory
pressure.
| >
| >
| > -- bruce (sqlwork.com)
| >
| >
| > "Billy Zhang" wrote:
| >
| > > Hi All,
| > >
| > > I am using asp.net session state service to store session.
| > > The concurrent online user will be almost 2000.
| > >
| > > Could asp.net session state service afford this?
| > > Is there any limitation about asp.net session state service?
| > >
| > > -Billy
|
 
Back
Top