I have a question,

My site is crashes still 2-3 times a day for unknown DNN reasons.  Until I figure this out, I'd like to go with multiple IIS worker processes.  The problem is, by enabling multiple processes, you run into some *serious* issues with cache.  Each worker process has its own cache that it uses.  Since DNN is heavily reliant on asp.net cache, this can cause some massive problems, such as hosing up a portal when you are editing it, and your edits happen to hit 2 different cache repositories, having modules which read in/out of cache now being not up to synch, etc.

So my question is:  How do you run multiple worker processes that use the same cache to DNN doesn't become out-of-synch?

Thanks.

PS - Yes, I've googled this up, however, I'm looking for feedback from people who have done this already with their DNN setup :)

I've searched everywhere but I cannot find the Web Farm Support document.  Could you please lend a hand?  Thx :)

Also, if you happen to know from experience, will this fix problems with w3wp.exe crashing?  For example, if I have a web farm with 3 w3wp.exe processes, and 1 instance crashes/bugs out, while all requests now go to the 2 healthly ones, or will it still be 2 health 1 bad requests?

For the application there is not much difference between 2 processes on different machines and 2 processes on the same machine, so you would setup dnn as if it were running in a web farm environment. The file based cache makes sure that all processes use the same cache...

Please let us know how you fare :)

cheers,

erik

DNN Blog | Twitter: @erikvb | LinkedIn: