Evan Huus
changed
bug 10245
| What |
Removed |
Added |
| Status |
UNCONFIRMED
|
CONFIRMED
|
| Hardware |
x86-64
|
All
|
| Version |
1.10.7
|
Git
|
| Ever confirmed |
|
1
|
| OS |
Windows 7
|
All
|
Comment # 4
on bug 10245
from Evan Huus
OK, so I've actually looked at the lua code and read your explanation on the
download page, and I'm wondering if you do manual adjustments after-the-fact
for network RTT, or if you just ignore that error?
Specifically:
- service time can only be accurately calculated if the trace was taken at the
server side, since otherwise you end up with 2xRTT extra time in the middle.
- request and response spread can only be accurately calculated if you have two
matching traces (one at client, one at server) because otherwise you end up
missing at least one RTT for each
Maybe this isn't important if your work is primarily on a LAN with negligible
RTT, but Wireshark is also used for traces with high RTT, which could throw off
these numbers significantly.
I'll leave this open, since I do think APDU response time is probably a useful
additional metric, though it's a very low-priority at the moment (especially
because there's now a lua plugin which already calculates that). It would be
nice if you could add the plugin (or a link to
http://www.tribelabzero.com/resources) to our Contrib page so that other users
looking for lua scripts can find it easily.
You are receiving this mail because:
- You are watching all bug changes.