« Previous Next »

Answered Thread: Slow Performance/Timer_MinBytesPerSecond in logs

Last post 04-10-2008 9:26 AM by AmrineA. 13 replies.

Average Rating Rate It (5)

RSS

Page 1 of 1 (14 items)

Sort Posts:

  • 12-12-2007, 3:00 PM

    • AmrineA
    • Not Ranked
    • Joined on 09-11-2007, 8:50 AM
    • Posts 7

    Slow Performance/Timer_MinBytesPerSecond in logs

    We recently brought up two new web servers. They are both running Windows Server 2003 x64 SP2 with 2 Quad core CPUs and 16 GB of RAM. These machines should really scream... However, ever since we've moved some clients over to them, they've been complaining that they are much slower than the older machines (which were using Windows Server 2003 32-bit). We've had a hard time diagnosing the problem. Here is what we do know?

    -The server isn't slow on every page and it isn't even consistently slow on the same page each time. Pages that run fast on other servers are sometimes extremely slow on this machine.

    -The HTTP log is producing a large number of Timer_MinBytesPerSecond entries for various pages...many of them being the ones that people are complaining about being slow.

    -On other boxes the HTTP log usually only has Timer_ConnectionIdle messages, which from what I understand don't really mean much of anything.

    -We copied the IIS configuration from one of the 32-bit boxes that was being replaced.

    -The ASP.NET application that runs on these servers is reporting reasonable times (we track how long it takes from when the request comes into the application to when the application finishes the request to find any bottlenecks in the application). So we are reasonably certain the problem does not lie within the application, but rather in the server/network configuration.

    -The hardware configuration is almost identical to two other web servers that we have been using for several months now with no problems.

     Any help is appreciated, and I will try to respond to any questions as quickly as I can.

  • 12-16-2007, 9:16 PM In reply to

    • Testius
    • Top 100 Contributor
    • Joined on 11-21-2006, 2:56 AM
    • Posts 59

    Answered Re: Slow Performance/Timer_MinBytesPerSecond in logs

    Hello,

    The first thing that I would try would be to make sure that the latest version of drivers for the NIC are being used.

    Also, as you using teaming or bonding?

    Cheers,
    Liam. 

  • 12-17-2007, 9:02 AM In reply to

    • AmrineA
    • Not Ranked
    • Joined on 09-11-2007, 8:50 AM
    • Posts 7

    Re: Slow Performance/Timer_MinBytesPerSecond in logs

    We installed all of the most up to date network drivers last week, and we haven't seen much, if any, improvement and the logs are still outputting Timer_MinBytesPerSecond in the logs. To be honest, I'm not entirely sure what teaming or bonding is? We don't usually setup the servers on the network (that's done by our ISP), but we have full remote desktop access to them in order to administer them (IIS, Windows, ASP.NET, etc.). If there is something I can check to get you your answer, I'll take a look.

  • 12-22-2007, 5:59 PM In reply to

    Re: Slow Performance/Timer_MinBytesPerSecond in logs

    Steve Schofield
    Windows Server MVP - IIS
    http://weblogs.asp.net/steveschofield


    http://www.IISLogs.com
    Log archival solution
    Install, Configure, Forget
  • 12-28-2007, 9:30 AM In reply to

    • AmrineA
    • Not Ranked
    • Joined on 09-11-2007, 8:50 AM
    • Posts 7

    Re: Slow Performance/Timer_MinBytesPerSecond in logs

    We've read similar articles like that before. Our application requires the use of more memory than the 32 bit platform allows, so 64 bit is our only option. Our two other systems that are performing well both run on 64 bit, so we know that isn't the problem.

  • 12-30-2007, 10:33 PM In reply to

    Re: Slow Performance/Timer_MinBytesPerSecond in logs

    Are you running the worker process in 32-bit or 64-bit? It is recommended to have 64bit OS, yet for wp you would be better off with multiple 32-bit w3wp.exe. and of coz it depends on app requirement.

    Cheers,
    Bernard Cheah
  • 12-31-2007, 9:09 AM In reply to

    • AmrineA
    • Not Ranked
    • Joined on 09-11-2007, 8:50 AM
    • Posts 7

    Re: Slow Performance/Timer_MinBytesPerSecond in logs

    We are running the worker process in 64-bit mode because we would have to run the state service to keep their session states synced between all of the different worker processes. There is serious performance degradation in doing this.

    I am interested in hearing more about how running 32-bit on 64-bit Windows is recommended... Please send along a link to a reference article/documentation.

  • 01-01-2008, 9:18 PM In reply to

    Re: Slow Performance/Timer_MinBytesPerSecond in logs

    You can search shared hosting in this site, though it is targeted on w2k8, it is applicable to w2k3 as well since 64bit wp uses more resources, etc. If you don't have native 64bit components running in 32-bit wp would be a better choice. Of coz again - test it first before changing the production box.

    Cheers,
    Bernard Cheah
  • 01-02-2008, 7:31 AM In reply to

    • AmrineA
    • Not Ranked
    • Joined on 09-11-2007, 8:50 AM
    • Posts 7

    Re: Slow Performance/Timer_MinBytesPerSecond in logs

    I'll have to research this more. However, I don't think that this will solve our problems since we have two almost identical servers that are running straight 64-bit and they are performing great without this issue.

  • 01-07-2008, 11:32 PM In reply to

    Re: Slow Performance/Timer_MinBytesPerSecond in logs

    Well, you can always have one run in 32 wp mode while the other run in native 64 bit, then stress test both boxes and compare the performance.

    Cheers,
    Bernard Cheah
  • 01-08-2008, 10:29 AM In reply to

    • AmrineA
    • Not Ranked
    • Joined on 09-11-2007, 8:50 AM
    • Posts 7

    Re: Slow Performance/Timer_MinBytesPerSecond in logs

    I have a little bit of addtional information that may help. We ended up reinstalling one of the servers and setting it back to it's basic settings. We didn't have any problems and performance was great. We then attempted to turn on dynamic compression and set compression level to the maximum, at this point, the errors started showing back up in the logs and the intermittent slow downs returned. The compression settings are the exact same as they are on two of the other 64-bit servers and we haven't had any issues. As soon as we turned dynamic compression off, everything went back to normal. Static compression is still enabled and doesn't seem to hurt anything. Below are the settings that we had that were causing problems.

     <IIsCompressionScheme Location ="/LM/W3SVC/Filters/Compression/gzip"
    HcCompressionDll="%windir%\system32\inetsrv\gzip.dll"
    HcCreateFlags="1"
    HcDoDynamicCompression="TRUE"
    HcDoOnDemandCompression="TRUE"
    HcDoStaticCompression="TRUE"
    HcDynamicCompressionLevel="0"
    HcFileExtensions="htm
    css
    xml
    js
    txt"
    HcOnDemandCompLevel="10"
    HcPriority="1"
    HcScriptFileExtensions="asp

    dll
    aspx
    ascx
    exe" />

     

  • 01-08-2008, 11:44 AM In reply to

    Re: Slow Performance/Timer_MinBytesPerSecond in logs

    Try setting your HcOnDemandCompLevel to 8, something less than 10 and test.  I've experienced issues when this setting to 10.  Try 7 or 8, which is what I use. 

    Steve Schofield
    Windows Server MVP - IIS
    http://weblogs.asp.net/steveschofield


    http://www.IISLogs.com
    Log archival solution
    Install, Configure, Forget
  • 03-19-2008, 3:42 PM In reply to

    • venkatap
    • Not Ranked
    • Joined on 03-19-2008, 7:33 PM
    • Posts 1

    Re: Slow Performance/Timer_MinBytesPerSecond in logs

    Hi AmrineA, your information was extremely helpful. I had to do disable Dynamic Compression on my server.

    I'm still interested to know more information on this issue, if you have any more information please feel free to forward it to me. At one point it was driving my crazy and finally able to find your information and it was extremely helpful.If you have any resolution to this problem please let me know, I still want it work with Dynamic compression ON. Thanks

    Venkat

     

     

     

     

  • 04-10-2008, 9:26 AM In reply to

    • AmrineA
    • Not Ranked
    • Joined on 09-11-2007, 8:50 AM
    • Posts 7

    Re: Slow Performance/Timer_MinBytesPerSecond in logs

    Since we had to use the box and didn't come up with a resolution, we ended up redoing the Windows Server 2003 install and giving the box a new name. For some reason, after doing that, everything has worked flawlessly. Something must have been messed up in the Windows configuration from Dell, or somehow having the same name as a previous computer on the network messed things up on the network. Either way, after doing the reinstall and giving it a new name, all is well.

Page 1 of 1 (14 items)
Microsoft Communities