As long as you've got connection pooling and a decent piece of hardware, you should be able to carry out all the non-trivial database queries you require, given an average application requirement.
The amount of user information you hold in their session is limited to the amount of available memory you have, divided by the expected absolute maximum number of concurrent sessions you predict. I am curious though due to the way you phrase you question, are you contemplating balancing the session memory usage against database usage dynamically? And another question, how much user info can you have in your application that is static enough to hold in their session? Regards Adam Richard Diaz wrote: >I'm currently doing DB Queries and holding the users >information in session objects... trying to keep the >query load on the database down to a minimum by using >these session objects (MVC2). > >My question is where do I draw the line as far as how >much RAM each user gets? When do I free up those >session objects and querying the database for >information again? > >Are there any guides on this? > >thanks in advance, >Rich > > > >__________________________________________________ >Do You Yahoo!? >LAUNCH - Your Yahoo! Music Experience >http://launch.yahoo.com > >-- >To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> >For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> > > > > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
