| Bug ID |
10245
|
| Summary |
Measurement of response time elements
|
| Classification |
Unclassified
|
| Product |
Wireshark
|
| Version |
1.10.7
|
| Hardware |
x86-64
|
| OS |
Windows 7
|
| Status |
UNCONFIRMED
|
| Severity |
Enhancement
|
| Priority |
Low
|
| Component |
Dissection engine (libwireshark)
|
| Assignee |
[email protected]
|
| Reporter |
[email protected]
|
Build Information:
Version 1.10.7 (v1.10.7-0-g6b931a1 from master-1.10)
--
It would be very useful if Wireshark reported service response times in the
following way:
* Service Response Time – First request packet to last response packet
* Request Spread – First request packet to last request packet
* Service Time – Last request packet to first response packet
* Response Spread – First response packet to last response packet
These values would be highly relevant since:
* Service Response Time measured adjacent to the client would provide an
instant view of Service Time plus any transport delays.
* Service Time measured adjacent to the service would provide an accurate
measure of the actual service time
* The Spread values would directly measure transport performance
The present measure Wireshark measure of Service Response Time changes
depending on the sub-dissector reassembly settings. Set one way you measure
Service Time plus Response Spread. Set the other way you get Request Spread
plus Service Time. These values are not useful for measuring overall
performance of the service plus the transport, or for measuring just Service
Time.
I'm no coder but I'd be willing to help in whatever way I can with this.
Best regards...Paul
You are receiving this mail because:
- You are watching all bug changes.
