restperfclient.log.gz
[NETCONF-169] RestPerfClient: Invalid requests rate reported when a thread times out Created: 22/Mar/16 Updated: 15/Mar/19 Resolved: 11/Apr/16 |
|
| Status: | Resolved |
| Project: | netconf |
| Component/s: | netconf |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | ||
| Reporter: | Jozef Behran | Assignee: | Jakub Morvay |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Operating System: All |
||
| Attachments: |
restperfclient.log.gz
|
| External issue ID: | 5580 |
| Description |
|
If a synchronous request sending thread aborts due to a timeout, the RestPerfClient still assumes it managed to send all requests and generates invalid "requests per second" value which is calculated as "scheduled count of requests" / "timeout in seconds" (if there is 1 thread, I did not test the behavior in a situation when there is more than one thread). This problem can be seen in the attached output log file. |
| Comments |
| Comment by Jozef Behran [ 22/Mar/16 ] |
|
Attachment restperfclient.log.gz has been added with description: Output from restperfclient where the bug was spotted. |
| Comment by Jozef Behran [ 31/Mar/16 ] |
|
To be precise, one acceptable (and expected) solution is this: Check for cancelled threads and if present, skip the calculation and display of the "requests per second" value. |
| Comment by Jakub Morvay [ 01/Apr/16 ] |