|
|
||
|
|
||
|
|
||
|
|
||
![]()
Product Support
Product Activation FAQs
Downloads
Maintenance Programs
White Papers
WildPackets Forums
Technical Compendium
Additional Resources
Tip of the Month
Wireless Tips
Plugin Tips
Product Versions
Networking Books
Networking Glossary
Networking Links
Tech Support Requests
|
March 2000Application response time analysisApplication response time analysis often involves more than just protocol analysis. If the network is error free, has plenty of bandwidth, and has low latency, check the server response time on the server's local segment. If, for example, you see an SQL server immediately send a TCP ACK packet in response to a client's SQL packet (such as a Sybase/Microsoft TDS packet), but the server's response TDS packet is several seconds later, the problem lies within the SQL server. Ensure that your analyzer and server clocks are set to the same time and log server utilization and SQL performance statistics using a utility such as NT's performance monitor (perfmon). Then, whenever you see a delayed TDS response packet in your analyzer you can correlate the time to the logged statistics such as CPU utilization, disk I/O, SQL cache hits, internal SQL transactions per second, etc., to help identify the bottleneck. |
|
||||||
| COPYRIGHT © 2008 WILDPACKETS, INC — PRIVACY STATEMENT · CONTACT US | CORPORATE · PRODUCTS · SOLUTIONS · SERVICES · SUPPORT · PARTNERS · BUY NOW |
|
All registered and unregistered trademarks are the sole property of their respective owners |
|
China
Japan
UK
United States



