I had various problems with my DNN site for a while, and I thought about formatting and revering to a previous version. However, the users have realized that everything is OK, but a day after. I investigated into the DB and realized that everything is actually there, but is not displayed (always) to the clients. Finally, I understood that there is a problem with caching, since if we edit anything it will show the next day. Tell me in what direction should I look to fix this problem since I'm stuck for now. Thank you!!! Configuration: Windows 2003 SP1 Net Framework 1.1.4322 DNN 3.3.2

I solved the problem!!!

I was using memory based caching. However, the actual problem lay in the configuration in the IIS, where we've put 4 workers in the Web Garden configuration. From what I saw, this potential performance boost is incompatible with a DNN site that is under heavy production. Everything else was operating, but the fact that you get randomly assigned worker meant that you MAY not see the changes until the cache is purged (or you get the same worker to send you the response). I took some time for us to realize this but as least now we know that this feature of IIS may not be utilized by DNN.

 

BTW thanks for the interest in answering our problem.

I have read that disk based caching is not efficient at all in comparison to it's memory-wise counterpart. Have you had any personal experience with file caching and would you recommend it for a low traffic site...? Thanks