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
Added for 'vardir' path disk disk utilization collecting routine which
parses file:
/proc/diskstats
for the value milliseconds spent doing I/Os from the given device
and counts 'busy' value in percents, like iostat tool does for its
'%util' field. Check for more information linux kernel documentation
[1]. We use from the 'diskstats' file Field 10 which is in real at
the 12th position:
Field 9 -- # of I/Os currently in progress
The only field that should go to zero. Incremented as requests are
given to appropriate struct request_queue and decremented as they
finish.
Field 10 -- # of milliseconds spent doing I/Os
This field increases so long as field 9 is nonzero.
Decided to collect 'vardir' disk utilization per each run test in
standalone file and print to stdout after testing completed, up to
10 most biggest of it.
To count 'vardir' disk utilization for each test we need to know what
was the value of the disk bound on the test start and time when test
started to count later the utilization. On test finish we check the
test finish time and current disk bound and count disk utilization.
All of these checks and counts implemented as the new routine
'get_disk_bound_stat_busy()' in 'lib/utils.py' file.
To collect disk bounds and durations on test start/finish events used
'StatisticsWatcher' listener which has the following usable routines
for it:
process_result()
Using 'WorkerCurrentTask' queue message receive event to save the
disk bounds values at the start of the tests.
Using 'WorkerTaskResult' queue message receive event to save final
disk bounds values for finished tests.
print_statistics() - statistics printing to stdout after testing.
Prints disk bounds for failed tests and up to 10 most used it tests.
We use standalone 'statistics' directory in 'vardir' path to save
'durations.log' file in it with disk bounds for each tested task
in format:
<test task name> <disk bound>
Needed for tarantool/tarantool-qa#97
[1]: https://www.kernel.org/doc/Documentation/iostats.txt
0 commit comments