Session state volume

[D. Harbison]

We are researching the following scenerio. 100,000 users
are signed into our system. Once every 5 seconds, each
user refreshes their data, giving us 20,000 hits/second.
Since we have a web server farm, we need a shared session
state environment. What is the best way to set up the
session state servers to handle this volume?

Thanks,
D. Harbison

[bruce barker]

two approaches

1) use mulitple sqlserver session managers. determine the state servers by
hashing the session guid. this requires all webservers to connect to all
session servers.

2) partition the appstate database across several sqlservers, and partition
by session guid. this way each webserver only connects to one sqlserver.

you can get about 200 simultaneous connections per webserver, assumimg 10k
payload , ave 2 sec network latency (everyone is on braodband), so your web
farm is about 200 servers, so I'd look at about 20 session servers (1
session server per 10 webservers).
-- bruce (sqlwork.com)


"D. Harbison" <an*******@disc ussions.microso ft.com> wrote in message
news:03******** *************** *****@phx.gbl.. .

We are researching the following scenerio. 100,000 users
are signed into our system. Once every 5 seconds, each
user refreshes their data, giving us 20,000 hits/second.
Since we have a web server farm, we need a shared session
state environment. What is the best way to set up the
session state servers to handle this volume?

Thanks,
D. Harbison