View Complete Thread
  • Re: Error 500.13 (Server too busy) with many sites on one machine

    Jun 02, 2010 04:29 PM|jn00s|LINK

    Hi armaita,

    First of all, I'm not 100% certain that this matters but just to be on the safe side, I would recommend that you always set your numbers in multiples of 1024.

    I also have been having to mess with these settings again recently, because I again started to get more 500.13 errors as the size of my website applications grows. I tried pushing them as high as 1024,4096,20480 but upon reboot I found that I had an error in the system event log - event ID 243, "A desktop heap allocation failed." So I tried scaling it back to 1024,3072,16384 and was able to reboot my servers and not get the allocation failed error. I also increased the SessionPoolSize and SessionViewSize to 100 and 200 to make more room for the larger heap numbers.

    I noticed that you are increasing your 2nd number, and this may be your problem. The 2nd number is for interactive heap, which is used by desktop applications. On a server you don't need very much of that, so try to get that number as low as possible without causing problems. The third number is the one you want to increase for non-interactive heap, which is used by services like IIS.

    I would suggest that you experiment with the following settings, and please post your results back.

    First, try using the default interactive value of 3072, while scaling the 3rd number upward in increments of 1024:

    1024,3072,1024
    1024,3072,2048
    1024,3072,3072
    1024,3072,4096
    1024,3072,5120
    1024,3072,6144
    1024,3072,7168
    1024,3072,8192
    1024,3072,9216
    1024,3072,10240
    1024,3072,11264
    1024,3072,12288
    1024,3072,13312
    1024,3072,14336
    1024,3072,15360
    1024,3072,16384

    Then, try the same thing but decrease the 2nd number in increments of 1024:

    1024,2048,1024
    1024,2048,2048
    1024,2048,3072
    1024,2048,4096
    1024,2048,5120
    1024,2048,6144
    1024,2048,7168
    1024,2048,8192
    1024,2048,9216
    1024,2048,10240
    1024,2048,11264
    1024,2048,12288
    1024,2048,13312
    1024,2048,14336
    1024,2048,15360
    1024,2048,16384

    ...

    1024,1024,1024
    1024,1024,2048
    1024,1024,3072
    1024,1024,4096
    1024,1024,5120
    1024,1024,6144
    1024,1024,7168
    1024,1024,8192
    1024,1024,9216
    1024,1024,10240
    1024,1024,11264
    1024,1024,12288
    1024,1024,13312
    1024,1024,14336
    1024,1024,15360
    1024,1024,16384

    Of course, you will probably not need to try ALL of those combinations (that would take a lot of reboots) so use your common sense... first scout out the range in increments of 4096, then you can observe the pattern and then you can fine tune down in increments of 2048 and 1024.

    One last thing, what else are you running on your servers besides IIS that might also be using up the heap?