Copied to clipboard

Flag this post as spam?

This post will be reported to the moderators as potential spam to be looked at


  • Connie DeCinko 931 posts 1160 karma points
    Sep 05, 2012 @ 20:16
    Connie DeCinko
    0

    Extremely High CPU = Nonresponsive Site

    We are stil having issues with high CPU which causes the site to become unresponsive. Sometimes purging logs helps, would like to know why. Also, deleting multiple versions.

    Would like to hear from others who experience this same issue when more than a few people are using the site. Especially when more than one person is editing content.

     

  • Drew 165 posts 340 karma points
    Sep 05, 2012 @ 21:14
    Drew
    0

    What setup are you using?
    (so server specification, server OS version, database, version of IIS, version of Umbraco)

    Have you got another site (Umbraco or plain ASP) running on that server, is it running just as slow?  

    Is there anything odd in the umbracoLog table - such as long periods between debug entries being written?

    Have tried adding ?umbDebugShowTrace=true onto one of your site URLs to see how long page elements are taking to render?


     What do you mean by "Deleting multiple versions" ? 

    Cheers,
    Drew 

  • Connie DeCinko 931 posts 1160 karma points
    Sep 06, 2012 @ 17:06
    Connie DeCinko
    0

    Windows Server 2003 R2, IIS V.6, SQL Server 2008 (different server), Umbraco 4.7

    No other sites running on this server.  When CPU pegs 100%, pages often don't display.  Nearly impossible to look in the Umbraco logs as a timeout error occurs before they open, unless I purge all but the last day or two.  Trace shows no elements taking a long time to render.

    By versions, I mean the versions of each page.  If a user makes changes and saves 50 times, we have 50 versions in the database.  If I purge all but the last 2 versions, it seems to help.

     

  • Connie DeCinko 931 posts 1160 karma points
    Sep 06, 2012 @ 19:37
    Connie DeCinko
    0

    As a follow up, I can't seem to figure out what happens during the End Load step.  On my dev server (below) I get quick rendering.

    aspx.page Begin Load 0.0610317791786386 0.000043
    aspx.page End Load 0.0811547277656797 0.020123
    aspx.page Begin LoadComplete 0.0813178769927463 0.000163
    aspx.page End LoadComplete 0.0813754262064033 0.000058
    aspx.page Begin PreRender 0.0814198452596629 0.000044
    aspx.page End PreRender 0.0815195786056608 0.000100
    aspx.page Begin PreRenderComplete 0.0815673500402984 0.000048
    aspx.page End PreRenderComplete 0.0818821945247231 0.000315
    aspx.page Begin SaveState 0.0857229061235436 0.003841
    aspx.page End SaveState 0.0859486331363344 0.000226
    aspx.page Begin SaveStateComplete 0.0859486331363344 0.000000
    aspx.page End SaveStateComplete 0.0859486331363344 0.000000
    aspx.page Begin Render 0.0861075918866783 0.000159
    aspx.page End Render 0.104540660894052 0.018

     

    On my production server (below), the times are horrible, same page, same hardware, same configuration.

    aspx.page Begin Load 0.238193401675353 0.000031
    aspx.page End Load 30.459103601156 30.220910
    aspx.page Begin LoadComplete 30.4591826614835 0.000079
    aspx.page End LoadComplete 30.4592164646624 0.000034
    aspx.page Begin PreRender 30.4592516646669 0.000035
    aspx.page End PreRender 30.4593326805502 0.000081
    aspx.page Begin PreRenderComplete 30.4593673218244 0.000035
    aspx.page End PreRenderComplete 30.4595980774093 0.000231
    aspx.page Begin SaveState 30.4625358809569 0.002938
    aspx.page End SaveState 30.4627180270118 0.000182
    aspx.page Begin SaveStateComplete 30.4627518301907 0.000034
    aspx.page End SaveStateComplete 30.4627828397185 0.000031
    aspx.page Begin Render 30.4628127317857 0.000030
    aspx.page End Render 30.4909825131406 0.028170

     

Please Sign in or register to post replies

Write your reply to:

Draft