« Previous Next »

• 04-27-2009, 5:57 AM

  stonoha Joined on 12-04-2008, 10:04 AM Posts 8

  standalone webserver, standalone database performance problem Reply Contact Hi, Im using wcat to stress test my webserver + database. I find the results a little bit confusing. At first I used the configuration: webserver + database on 1 PC: I was able to gain 70 requests per 1 second. 1 % of them returned with error status 500 - time out (no problem). Then I tried configuration: webserver: 1 PC, database: another PC: I was able to make 80 requests per second, but 3% of them returned with error status 500. Also "Average Time to First Byte" was 2x bigger than in first case. Both computers are members of company's lan network (100 Mb\sec) so bandwidth is not the issue, as long as network transfer during my tests did not exceed 10 Mb\sec (and i practically used to send data with 50 Mb \sec speed on this lan).  Does anybody know what might be the problem? I allways believed that configuration with standalone database should perform better. Thanks for any advice. --Martin

  Tags: WCATperformancespeed problemwebserverstandalone database

• 05-04-2009, 12:00 AM

  In reply to

  Leo Tang - MSFT Joined on 12-11-2008, 9:47 PM Posts 939

  Re: standalone webserver, standalone database performance problem Reply Contact Hi, I'd suggest you enable the Failed Request Tracing feature for the two scenarios, then create a tracing rule for the 500 error. The Failed Request Tracing logs will record the time spent on each module. You can find more clues through comparing the output in the Failed Request Tracing logs on the server. Leo Tang Microsoft Online Community Support Please remember to mark the replies as answers if they help and unmark them if they provide no help.