Important Notice from AspDotNetStorefront
It is with dismay that we report that we have been forced, through the action of hackers, to shut off write-access to this forum. We are keen to leave the wealth of material available to you for research. We have opened a new forum from which our community of users can seek help, support and advice from us and from each other. To post a new question to our community, please visit: http://forums.vortx.com
Results 1 to 5 of 5

Thread: Low performance on IIS 7.0

  1. 01-21-2010, 05:22 PM #1
    sergeytest is offline Junior Member
    Join Date
    Jan 2010
    Posts
    2

    Default Low performance on IIS 7.0

    Could be a misconfiguration on our part, but it looks like the site was performing well until moved into production environment IIS7, where the symptoms are as follows.

    Opening default.aspx takes approx 24 sec (timed with IEWatch). After which for the same user the system is responsive under 2 sec response time as long as you keep clicking through the application with 15-20 sec between clicks, as soon as you are away for about 1-2 minutes, the first request after that takes over 20 sec again. At that time there is high CPU utilization on the server.
    The problem is not reproduced in the development or staging environment.

    Cash Menus = True
    Session timeout is 3600
    compilation debug (web.config) is false.

    Tried caching dynamic content, without any luck.

    Not sure what else to change, but it looks like the pages are being recompiled again and again.

    If you have ideas please let me know.
    Thank you in advance
  2. 01-21-2010, 07:59 PM #2
    George the Great is offline Senior Member
    Join Date
    Nov 2006
    Location
    Cleveland, OH
    Posts
    1,792

    Default

    Could you provide some additional information about the setup and the environment?

    • Which version of AspDotNetStorefront are you using?
    • Are you running in Integrated Pipeline or Classic mode?
    • How many other sites exist in the same application pool?
    • Is this a shared hosting environment?
    • How big is the application pool?
    • What is the time period between application pool resets/recycles?
    • Have you looked in the event logs to see if there are any errors that stand out?
    <a href="http://www.aspdotnetstorefront.com">Shopping Cart Software</a>
  3. 01-21-2010, 08:38 PM #3
    sergeytest is offline Junior Member
    Join Date
    Jan 2010
    Posts
    2

    Default performance on IIS 7.0

    Could you provide some additional information about the setup and the environment?

    * Which version of AspDotNetStorefront are you using?
    * Are you running in Integrated Pipeline or Classic mode?
    * How many other sites exist in the same application pool?
    * Is this a shared hosting environment?
    * How big is the application pool?
    * What is the time period between application pool resets/recycles?
    * Have you looked in the event logs to see if there are any errors that stand out?


    * storefront ML/64
    * I suspect Classic (not sure how to tell)
    * single site, on a standalone server hosting both IIS and MS SQL 2005 Express
    * not shared with anyone else
    * separate application pool for storefront app, no other apps deployed
    * 1740 minutes (I suspect this is a default)
    * there are some errors saying that application pool exceeded its job limit settings, but that was just once throughout 4 hour testing cycle while the problems were experienced throughout the testing.
  4. 01-21-2010, 10:05 PM #4
    Kirk48906 is offline Member
    Join Date
    Jan 2009
    Posts
    67

    Default

    I'd love to know the answer to this too. We have similar issues on our 7.0 server.
  5. 05-26-2011, 03:13 PM #5
    sshapiro is offline Junior Member
    Join Date
    May 2011
    Posts
    16

    Default

    Anyone have any further info on this? I am seeing pretty spotty performance in IIS7 as well.

    Random CPU utilization spikes of 99%. Random pages taking a while to load. And then the next request loading almost instantly.

    Running on a dedicated webserver with a dedicated SQL server separate.