* Sasha Levin <levinsasha928@xxxxxxxxx> wrote: > Benchmarks ran on a seperate (non boot) 1GB virtio-blk device, > formatted as ext4, using bonnie++. > > cmd line: > # bonnie++ -d temp/ -c 2 -s 768 -u 0 > > Before: > Version 1.96 ------Sequential Output------ --Sequential Input- --Random- > Concurrency 2 -Per Chr- --Block-- -Rewrite- -Per Chr- --Block-- --Seeks-- > Machine Size K/sec %CP K/sec %CP K/sec %CP K/sec %CP K/sec %CP /sec %CP > tux 768M 498 99 381127 74 269712 48 2871 99 717109 50 +++++ +++ > Latency 18368us 31063us 21281us 3017us 6875us 251ms > Version 1.96 ------Sequential Create------ --------Random Create-------- > tux -Create-- --Read--- -Delete-- -Create-- --Read--- -Delete-- > files /sec %CP /sec %CP /sec %CP /sec %CP /sec %CP /sec %CP > 16 +++++ +++ +++++ +++ +++++ +++ +++++ +++ +++++ +++ +++++ +++ > Latency 148us 588us 2792us 1547us 1543us 218us > > After: > Version 1.96 ------Sequential Output------ --Sequential Input- --Random- > Concurrency 2 -Per Chr- --Block-- -Rewrite- -Per Chr- --Block-- --Seeks-- > Machine Size K/sec %CP K/sec %CP K/sec %CP K/sec %CP K/sec %CP /sec %CP > tux 768M 499 99 459779 73 350689 54 2997 99 860395 58 +++++ +++ > Latency 17194us 14619us 26358us 4055us 7890us 44122us > Version 1.96 ------Sequential Create------ --------Random Create-------- > tux -Create-- --Read--- -Delete-- -Create-- --Read--- -Delete-- > files /sec %CP /sec %CP /sec %CP /sec %CP /sec %CP /sec %CP > 16 +++++ +++ +++++ +++ +++++ +++ +++++ +++ +++++ +++ +++++ +++ > Latency 135us 567us 2564us 134us 1500us 231us In such cases it would *really* be useful, in addition of dumping 80-100 raw numbers to summarize results and compare them for the reader, as i suspect you've done already? Please don't keep it a secret and don't force the reader to compare two tables with 80+ raw numbers! :-) Something like: " In short, block writes are 20% faster, block reads are 19.9% faster, seeks got 16% faster. None of the operations got slower. " Thanks, Ingo -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
