# dd if=/dev/urandom of=/mnt/s3ql/Varasto_2/testi2  bs=1M count=300
300+0 tietuetta sisään
300+0 tietuetta ulos
314572800 tavua (315 MB) kopioitu 45,4556 sekunnissa, 6,9 MB/s
# dd if=/dev/urandom of=/mnt/s3ql/Varasto_2/testi2  bs=1M count=100
100+0 tietuetta sisään
100+0 tietuetta ulos
104857600 tavua (105 MB) kopioitu 14,0052 sekunnissa, 7,5 MB/s


# s3ql/s3ql-2.15/contrib/benchmark.py swift://sensored/ 
/home/riku/TNC_Test_Ver-1.1.iso07.cdr --threads 3
Preparing test data...
Measuring throughput to cache...
Cache throughput with   4 KiB blocks: 15739 KiB/sec
Cache throughput with   8 KiB blocks: 20506 KiB/sec
Cache throughput with  16 KiB blocks: 24010 KiB/sec
Cache throughput with  32 KiB blocks: 26103 KiB/sec
Cache throughput with  64 KiB blocks: 27438 KiB/sec
Cache throughput with 128 KiB blocks: 27952 KiB/sec
Measuring raw backend throughput..
Backend throughput: 8058 KiB/sec
Test file size: 31.19 MiB
compressing with lzma-6...
lzma compression speed: 2192 KiB/sec per thread (in)
lzma compression speed: 363 KiB/sec per thread (out)
compressing with bzip2-6...
bzip2 compression speed: 11196 KiB/sec per thread (in)
bzip2 compression speed: 2719 KiB/sec per thread (out)
compressing with zlib-6...
zlib compression speed: 26023 KiB/sec per thread (in)
zlib compression speed: 8012 KiB/sec per thread (out)

With 128 KiB blocks, maximum performance for different compression
algorithms and thread counts is:

Threads:                              1           2           3           
4           8
Max FS throughput (lzma):     2192 KiB/s   4384 KiB/s   6576 KiB/s   8769 
KiB/s  17538 KiB/s
..limited by:                       CPU         CPU         CPU         
CPU         CPU
Max FS throughput (bzip2):   11196 KiB/s  22393 KiB/s  27952 KiB/s  27952 
KiB/s  27952 KiB/s
..limited by:                       CPU         CPU   S3QL/FUSE   
S3QL/FUSE   S3QL/FUSE
Max FS throughput (zlib):    26023 KiB/s  26170 KiB/s  26170 KiB/s  26170 
KiB/s  26170 KiB/s
..limited by:                       CPU      uplink      uplink      
uplink      uplink

All numbers assume that the test file is representative and that
there are enough processor cores to run all active threads in parallel.
To compensate for network latency, you should use about twice as
many upload threads as indicated by the above table.

kib means kibibyte or kilobyte?

-- 
You received this message because you are subscribed to the Google Groups 
"s3ql" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to