I'm having an incredibly hard time selecting an option to go with that suits my apps needs and would love some insight from some seasoned veterans. I'm working with rather limited server resources as far as memory is concerned and a 100'000 + userbase with potentially 40'000+ concurrent users at peak times. To reserve memory usage, I use strict cookie-based sessions, only use view state and control state were absolutely necessary and caching of any data/pages that rarely change and are used frquently, however this doesn'y accoutn for much since atleast 80% of the site is based on dynamic data.
The problem is in regards to storing search results in a per-user basis. I am trying to deveolp this in a way that uses as little server resources as possible. The search results are returned in an array of custom objects that contain a single Guid value and a byte value for each result. The total number of results per search can range anywhere from only a few hundred up to 4000+. Thes ...
Go to the complete details ...