You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently our summary output includes sections like:
| All | Total refresh time | | 131.531 | min |
| All | Min refresh time per shard | | 43.0791 | min |
| All | Median refresh time per shard | | 44.0437 | min |
| All | Max refresh time per shard | | 44.4079 | min |
i.e. only times not count.
Given #608 we can't rely too much on node-stats atm, so makes sense to also present the Total refreshes / Total merges (maybe an avg rate too based on total time?)
The text was updated successfully, but these errors were encountered:
Due to elastic#608 it's likely we need to benchmark scenarios without using
the node-stats telemetry device. At the same time we want to get a
general idea of how many refreshes/merges/flushes happened (in total)
by accessing the index stats.
Add total count for merges/refresh/flush in summary output; this is
collected from `_all/primaries` in `_stats`.
Also modify summary description to clarify the values are totals from
primary shards.
Finally fix bug where index stats where time/count == 0 got skipped
from the summary.
Closeselastic#614
Due to #608 it's likely we need to benchmark scenarios without using
the node-stats telemetry device. At the same time we want to get a
general idea of how many refreshes/merges/flushes happened (in total)
by accessing the index stats.
Add total count for merges/refresh/flush in summary output; this is
collected from `_all/primaries` in `_stats`.
Also that these values are cumulatives from primary shards and also
clarify desciprion for min/median/max in the summary report.
Finally fix bug where index stats where time/count == 0 got skipped
from the summary.
Closes#614
Relates: #615
Relates: elastic/elasticsearch#35594 (comment)
Currently our summary output includes sections like:
i.e. only times not count.
Given #608 we can't rely too much on node-stats atm, so makes sense to also present the
Total refreshes
/Total merges
(maybe an avg rate too based on total time?)The text was updated successfully, but these errors were encountered: