asp.net - Proof that Web Gardens do not fly well with InProc Sessions -


i tinkering web gardens in asp.net iis 6.0. multiple sources (source1 source2) explain how inproc session not fly web gardens. built program prove it, results difficult explain. please me explain results of testing.

test
set maximum # of worker processes 1000 in iis. create web app stores string in session , retrieves value button click. run web app in ie, ff, , blackberry browsers.

result
ie: pulls session properly. session failed after letting website sit idle ~3 minutes.
ff: session never failed. after sitting ~15 minutes session failed.
bb: regularly fails. ratio inline source2 says. greater # of worker processes in garden, more session fails.

my interpretation
ff/ie/desktop browsers have more memory may allows better caching.

notes
setting ie check newer versions of page on every visit has no effect. noticed postbacks blackberry pretty guaranteed create new instance of w3wp.exe, whereas mem usage increased same w3wp.exe process postbacks ie/ff.

the fact browsers have more memory shouldn't have inproc sessions , webgardens server side components.

you see more issues increase number of worker processes because more number of worker processes less request handled same worker process when comes back. in other words if have 1 worker process have 1 in 1 chance go same worker process on second request; if have 2 worker processes have 1 in 2 chances, if have 3 worker process have 1 in 3 chances, , on.

i wonder why trying use inproc sessions, though. there no reason can vanish easily. see article http://www.west-wind.com/weblog/posts/1986.aspx


Comments

Popular posts from this blog

Add email recipient to all new Trac tickets -

400 Bad Request on Apache/PHP AddHandler wrapper -

php - Change action and image src url's with jQuery -