locked
Maximum used memory setting in Sharepoint Application pool RRS feed

  • Question

  • Hi,

            We have a 32 bit Intel xeon processor that houses 15GB of RAM in the Production environment.We have an instance of MOSS 2007 .

    The Application pool that hosts the SSP for performing search/crawl gets heavy and consumes so much of memory while doing a full crawl. The Memory Recycle properties of the app pool shows unchecked "maximum virtual memory"  and  "maximum used memory" .

    Will setting the maximum usable memory to some 9GB help the Processor intensive crawl operation ?

    Since the maximum value is not set(unchecked checkbox),does it mean that the app pool has access to the entire RAM capacity?Or does the app pool recycle after a predefined RAM limit usage ?

    Regards,

    Grigory

    Tuesday, June 19, 2012 2:38 PM

Answers

  • We are running Windows Server 2003 Enterprise Edition which is a 32 bit version. The Processor is also a 32 bit one. I believe ,by default the processor can utilize 2^32 = 4GB of RAM.So will the installed 15GB be of practical use ?

    ...

    The main issue is that , While running Full crawl over the Content Source, we get over 700 errors that states "Error in the Site Data Web Service. (Exception of type 'System.OutOfMemoryException' was thrown.) " .

    We were pondering whether it is related to : 

    1.App pool recycling due to insufficient memory , or

    2.Lack of some crawler impact rule, as simultaneous requests might overload the site causing memory exception.

    It is a direct result of the server running out of memory. With Windows Server 2003 Enterprise x86 with the /PAE switch you can allocate up to 64 GB of memory if your system supports it. In all honesty though, you are likely looking at migrating the farm to servers running a 64-bit OS.

    Increasing the values in IIS will not overcome this limitation.


    Jason Warren
    Infrastructure Specialist

    Wednesday, June 20, 2012 4:48 PM

All replies

  • What OS is the server running? Your mention of a 32-bit processor indicates to me that the OS is 32-bit... Are you using the /PAE boot.ini switch?

    To answer your question, by not enabling the maximum virtual memory or maximum used memory options, IIS will use as much memory as it can allocate. By limiting this to 9 GB you don't allow it to consume more than this. According to a post on forums.iis.net, the maximum amount of memory a 32-bit application pool can use is 800 MB. I'm don't know if this is true.

    What else is running on this server? Is SQL Server on this server as well?


    Jason Warren
    Infrastructure Specialist


    Wednesday, June 20, 2012 12:59 AM
  • With 32- bit i don't think you can user more than approx 3.6 Gb of Ram. Thats the max memory you can use on 32 Bit m/c.

    Thats right you can use max of 800MB of ram per app pool. i had also read this on Joel's Old  blog about capacity planning.


    Aniket


    Wednesday, June 20, 2012 5:12 AM
  • You can reduce the load by using more content sources and change the incremental and full crawl schedule.
    You can also exclude  urls like the one which ends with items.aspx and so on which will reduce the load on crawls.

    Aniket

    Wednesday, June 20, 2012 5:16 AM
  • Hi Jason,

                      We are running Windows Server 2003 Enterprise Edition which is a 32 bit version. The Processor is also a 32 bit one. I believe ,by default the processor can utilize 2^32 = 4GB of RAM.So will the installed 15GB be of practical use ?

    This is a front end server. We dont have any instances of SQL server installed here.

    The main issue is that , While running Full crawl over the Content Source, we get over 700 errors that states "Error in the Site Data Web Service. (Exception of type 'System.OutOfMemoryException' was thrown.) " .

    We were pondering whether it is related to : 

    1.App pool recycling due to insufficient memory , or

    2.Lack of some crawler impact rule, as simultaneous requests might overload the site causing memory exception.

    Regards,

    Grigory

    Wednesday, June 20, 2012 6:21 AM
  • We are running Windows Server 2003 Enterprise Edition which is a 32 bit version. The Processor is also a 32 bit one. I believe ,by default the processor can utilize 2^32 = 4GB of RAM.So will the installed 15GB be of practical use ?

    ...

    The main issue is that , While running Full crawl over the Content Source, we get over 700 errors that states "Error in the Site Data Web Service. (Exception of type 'System.OutOfMemoryException' was thrown.) " .

    We were pondering whether it is related to : 

    1.App pool recycling due to insufficient memory , or

    2.Lack of some crawler impact rule, as simultaneous requests might overload the site causing memory exception.

    It is a direct result of the server running out of memory. With Windows Server 2003 Enterprise x86 with the /PAE switch you can allocate up to 64 GB of memory if your system supports it. In all honesty though, you are likely looking at migrating the farm to servers running a 64-bit OS.

    Increasing the values in IIS will not overcome this limitation.


    Jason Warren
    Infrastructure Specialist

    Wednesday, June 20, 2012 4:48 PM