Stump the Panel » Site Managers and Site Collection Managers

w3wp.exe size

(5 posts)

Tags:

  1. JasonD
    Member

    We are currently implementing a WCM Portal that consists of over 2000 sites and approximately 20 000 articles. We are still finalising the development but are working on one of our production servers. (64bit Blade server with 32Gb RAM)
    The environment is extremely fast but gradually slows down every morning. What we do tend to find is that the w3wp.exe process continues to grow in size. This morning it was over 24 GB. I assume that this should not be happening. Can anyone help me out with this. Please let me know what additional details you require.

    Thanks in advance.

    Posted 3 days ago #
  2. It is hard to say what is causing the problem without examining your server in more detail. Since you are still developing it, app pool should not get near 24 GB.

    Take a look at your app pool configuration and configure it as Joel describes here: http://blogs.msdn.com/joelo/archive/2007/10/29/sharepoint-app-pool-settings.aspx

    Posted 2 days ago #
  3. Toekiller
    Member

    I'm experiencing something strange with w3wp.exe too. The other day I started to get out of memory errors and webparts unable to load.

    Earlier in the day I had created 3 webparts ( using SPD ) connected to a library filtering on content types. I can watch the w3wp.exe expand, sometimes as much as 5 meg a time, as I load and refresh the page with these webparts. It doesn't seem to release the memory.

    The library in question has 350 documents and I group by 2 tree levels.

    The original webparts pointed at the same library and created normally using the web browser do not exhibit the same behaviour.

    Any idea's?

    Outside of this, I did find that the speed of the initial load was improved by removing the default parameters it creates when you start to create the dataview.

    Posted 2 days ago #
  4. These kinds of highly technical configuration questions are often asked on the MSDN forums. I don't see any harm posting them here, but I'd also look to the MSDN forums because you get a lot of developers looking at these kinds of issues.

    You may get some good answers there too, so I'd post them there for more exposure.

    Posted 1 day ago #
  5. Do you guys have any custom programming involved in any of your work? It's easy to introduce memory leaks with custom code if you don't follow certain rules and guidelines. That would explain the memory problem.

    I have also seen some funny app pool configurations cause problems too. Did you play around with your app pool config?

    Posted 1 day ago #

RSS feed for this topic

Reply

You must log in to post.