Actions
Bug #1210
closedglobal counters in stats.log
Affected Versions:
Effort:
Difficulty:
Label:
Description
All global counters in stats.log should be global not per thread printed.
Example - http.memuse
It is extremely misleading during trouble shooting and/or monitoring of a deployment to have global counters printed on per-thread basis - especially when the actual value differs for each thread. (due to sync when writing it)
It wrongfully gives the impression that the particular value occurs with regards to that particular thread's performance.
Updated by Victor Julien over 9 years ago
- Status changed from New to Closed
- Assignee set to Victor Julien
- Target version changed from 3.0RC2 to 3.0RC1
- % Done changed from 0 to 100
Actions