fileio 'prepare' should print elapsed time

Bug #1397847 reported by Alexander Sashnov
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
sysbench
Invalid
Undecided
Unassigned

Bug Description

fileio 'prepare' should print elapsed time because it can be used also as a test.

I'm comparing Ubuntu 64 bit running on host and inside of VirtualBox. In VirtualBox it is very slow and I want to figure out what's presicely wrong with it.

So instead of just:

 $ sysbench --test=fileio prepare
 sysbench 0.4.12: multi-threaded system evaluation benchmark

 128 files, 16384Kb each, 2048Mb total
 Creating files for the test...
 $

I want to see elapsed time and approximately MB/seconds for file creation.

Revision history for this message
Alexey Kopytov (akopytov) wrote :

This has already been requested and implemented in the 0.5 branch (aka trunk):

$ ./sysbench --test=fileio prepare
sysbench 0.5: multi-threaded system evaluation benchmark

128 files, 16384Kb each, 2048Mb total
Creating files for the test...
Extra file open flags: 0
Creating file test_file.0
Creating file test_file.1
...
Creating file test_file.126
Creating file test_file.127
2147483648 bytes written in 50.53 seconds (40.53 MB/sec).

Changed in sysbench:
status: New → Invalid
Revision history for this message
Alexander Sashnov (sashnov) wrote :

Cool!
But may be it is not a good idea to print 128 lines if --verbose is not specified.

Revision history for this message
Alexey Kopytov (akopytov) wrote :

May be it is not. If I remember correctly, it was requested by someone to reuse files. As in, you can start creating files, which may take some time. That process can be interrupted for whatever reasons. On subsequent "sysbench --test=fileio prepare" already created files should be reused, but then people want to know which ones have been reused, and which ones have been created from scratch.

I don't mind raising verbosity for those messages, so they are not printed by default. Please file a separate request if you need it.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.