Maintaining Session between Pages on 1000 User Hits

Hi vaibhav,

If our website is having the husge hits then we call the site with theterm "Web Garden".

For this type of the applications, To maintain the session we use "SQL Server" mode.

Before entering into sql server session details let me expain how web garden type of apps behave :

Let us think that 1000 users is huge hits to our app.

User 1 ---> reuest goes to server. session creates.

User 2 ---> reuest goes to server. session creates.

User 3 ---> reuest goes to server. session creates.

----------------------------------------------------

---------------------------------------------------

User 1000 ---> reuest goes to server. session creates.

Remember the server maintains the "Q" like First come First serve.

Untill the response sends to the previous user it wont accept any request from the new requested user.

So, the waiting time willbe more. (Hahaaaa here comes the frustration for the user, as it will be loading onnn...)

To overcome this type of situation we are using the "load balance" concept.

Load balance means maintaing the same application in multiple servers.

If there are multiple servers the request can be sent to the another server instead of waiting.

Now, If we use Inproc server session the problem raises.

Howwwwwwwwwww ?

Let us think that first time your request accepted by server1.

Second time due to the "Q" large number(1000 users) hits our request might recieve 2nd server.

Then how come the session can be remembered ? Because our session is created by 1st server.

So, For this type of case we needs to choose the SQL Server mode. So that the session will be stored in the database.

Hope you understood.

If you understood mark as answer.

Thank you.

1 Reply

Know the answer? Post it — somebody with the same question will find it here.

Sreekanth Reddy7y ago
Accepted answer
Hi vaibhav,

If our website is having the husge hits then we call the site with theterm "Web Garden".
For this type of the applications, To maintain the session we use "SQL Server" mode.
Before entering into sql server session details let me expain how web garden type of apps behave :
Let us think that 1000 users is huge hits to our app.
User 1 ---> reuest goes to server. session creates.
User 2 ---> reuest goes to server. session creates.
User 3 ---> reuest goes to server. session creates.
----------------------------------------------------
---------------------------------------------------
User 1000 ---> reuest goes to server. session creates.
Remember the server maintains the "Q" like First come First serve.
Untill the response sends to the previous user it wont accept any request from the new requested user.
So, the waiting time willbe more. (Hahaaaa here comes the frustration for the user, as it will be loading onnn...)
To overcome this type of situation we are using the "load balance" concept.
Load balance means maintaing the same application in multiple servers.
If there are multiple servers the request can be sent to the another server instead of waiting.
Now, If we use Inproc server session the problem raises.
Howwwwwwwwwww ?
Let us think that first time your request accepted by server1.
Second time due to the "Q" large number(1000 users) hits our request might recieve 2nd server.
Then how come the session can be remembered ? Because our session is created by 1st server.
So, For this type of case we needs to choose the SQL Server mode. So that the session will be stored in the database.
Hope you understood.
If you understood mark as answer.
Thank you.