w3wp.exe issue for asp.net Application

  • [font="Times New Roman"]Hallo Everyone,

    I am using an asp.net v2.0 application for which application pool, web site is created.

    Every day multiple users logged into application for doing transactions doing this in Activity Monitor I came to know that w3wp.exe is taking more than 350 MB of Memory Usage. Due to which application performance is sucked. Generally I restart IIS when the process(w3wp.exe) consumed 550 MB of Memory Usage. This occurs on daily basis no matter whether transactions is going on or not..

    So I want to know Is their any permanent solution ??[/font]

  • bhushan_juare (9/13/2012)


    [font="Times New Roman"]Hallo Everyone,

    I am using an asp.net v2.0 application for which application pool, web site is created.

    Every day multiple users logged into application for doing transactions doing this in Activity Monitor I came to know that w3wp.exe is taking more than 350 MB of CPU size. Due to which application performance is sucked. Generally I restart IIS when the process(w3wp.exe) consumed 550 MB of CPU. This occurs on daily basis no matter whether transactions is going on or not..

    So I want to know Is their any permanent solution ??[/font]

    I am a bit confused by your post on a number of counts. First of all this appears to in no way be related to sql server at all. In fact, I would hope that your website is not on the same server.

    You talk about a process taking up space in the CPU. I am quite confused by that. I assume you mean memory and not CPU? It seems that your application is not release objects as it should be. We have some incredibly busy sites and the worker process never gets anywhere near that size. 150 - 200MB during high peaks.

    You ask if there is a permanent solution but there is no way to tell what the problem is yet.

    _______________________________________________________________

    Need help? Help us help you.

    Read the article at http://www.sqlservercentral.com/articles/Best+Practices/61537/ for best practices on asking questions.

    Need to split a string? Try Jeff Modens splitter http://www.sqlservercentral.com/articles/Tally+Table/72993/.

    Cross Tabs and Pivots, Part 1 – Converting Rows to Columns - http://www.sqlservercentral.com/articles/T-SQL/63681/
    Cross Tabs and Pivots, Part 2 - Dynamic Cross Tabs - http://www.sqlservercentral.com/articles/Crosstab/65048/
    Understanding and Using APPLY (Part 1) - http://www.sqlservercentral.com/articles/APPLY/69953/
    Understanding and Using APPLY (Part 2) - http://www.sqlservercentral.com/articles/APPLY/69954/

  • A number of points here.

    If your web application runs all its SQL activity in a single transaction, then recycling the worker process should not cause any problems.

    However if you have 2 SQL transactions for example

    User Request

    Transaction 1 UPDATE table A

    Transaction 2 UPDATE table B

    Serve Page

    Then recycle could conceivably happen between the 2 transactions, leaving you with an incomplete update. Its even more likely if Transaction 1 is taking a long time.

    And monitor the number of .NET connections to the SQL Server - if it goes up and up, check the application code for proper closing and disposal of connections. Perhaps you want set a connection pool limit.

    And finally under application pool defaults, there are many settings to configure so you don't have to recycle manually. You can set automatic recycling to occur at a time limit, at specific times of day, and after a set number of requests. You can also limit the memory or cpu of an application pool. - But first of all try to find out why it is growing too large.

Viewing 3 posts - 1 through 2 (of 2 total)

You must be logged in to reply to this topic. Login to reply