Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
currently we are using Sessions to store datatables in our pages so that we don’t have to make Database hits to get the same datatable again and again. But my worry is that it is using the server memory and if large number of users login some day, the response of the server will become slow and our application might crash as well.
Please tell me is it a good idea to store datatables into Sessions or should we get the datatables from DB everytime?
As a general rule of thumb I would say don’t use session. I haven’t had to use session for a long time. As soon as you move into a web farm situation session either gets a lot slower or a lot more complicated or both.
Whether you will get away with it or not really depends on how much data you are storing in session, and how many users will be active within the session timeout period.
There are a lot of caching and in memory database options available today that may be a better option. Finally, while the solution as described sounds questionable, I wouldn’t optimize the existing solution until you have actually measured a problem.