Also you can use Fiddler to look at the http responses from a client
prespective to see if you can capture the 400/500 errors. You can even
see which script or url sequence is taking the longest as it looks from
the client, and reissue that request after you make changes to see if
the performance is helping. 

 

Also need to hook up filemon and regmon to the W3wp.exe process that is
running in the web application pool(s) that are running under the
website. Also look at any issues with the backend database if you are
using one for the website, which might be your problem if you are
dealing with locking/blocking or slow website performance due to DB
issues. Also the stuff at Ken's site (IISSTATE and others will prove
useful) 

 

Are you seeing any specific errors in the IIS logs ( like 400.X or
500.x) or the httperr.log  (Look at 

http://msdn.microsoft.com/en-us/library/aa954365.aspx) 

 

Z

 

Edward Ziots

Network Engineer

Lifespan Organization

MCSE,MCSA,MCP+I, ME, CCA, Security +, Network +

[email protected]

Phone:401-639-3505

________________________________

From: Michael B. Smith [mailto:[email protected]] 
Sent: Thursday, July 02, 2009 5:08 PM
To: NT System Admin Issues
Subject: RE: troubleshooting website performance

 

I would start with web analytics software so you can determine which
transactions are specifically at issue, concurrent with that - what does
perfmon have to say?

 

________________________________

From: Andy Shook [[email protected]]
Sent: Thursday, July 02, 2009 4:44 PM
To: NT System Admin Issues
Subject: troubleshooting website performance

Server 2003 SP2

Newer IBM something or other 

2.8Ghz dual core

1.5GB RAM

7 disk  (2 in a RAID1 four in a RAID5 with a hot spare)

 

Server is paging at 1.14GB continually and page file is set to 768MB in
size.

 

Performance issue on website response.  Server literally takes 20-30
seconds to response to request sent by the firewall before firewall
forwards response to user on the Interwebs.  Mucho time spent with
wireshark analyzing packet traces to show that the firewall is receiving
the request from the WAN and promptly forwards http request to internal
web server.  Web server response takes forever to respond,
troubleshooting now but wanted to throw this out to the collective...

 

TIA,      

 

Shook

 

 

 

 

 

~ Finally, powerful endpoint security that ISN'T a resource hog! ~
~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/>  ~

Reply via email to