> statfile1                 988ops/s   0.0mb/s      0.0ms/op       22us/op-cpu
> deletefile1               991ops/s   0.0mb/s      0.0ms/op       48us/op-cpu
> closefile2                997ops/s   0.0mb/s      0.0ms/op        4us/op-cpu
> readfile1                 997ops/s 139.8mb/s      0.2ms/op      175us/op-cpu
> openfile2                 997ops/s   0.0mb/s      0.0ms/op       28us/op-cpu
> closefile1               1081ops/s   0.0mb/s      0.0ms/op        6us/op-cpu
> appendfilerand1           982ops/s  14.9mb/s      0.1ms/op       91us/op-cpu
> openfile1                 982ops/s   0.0mb/s      0.0ms/op       27us/op-cpu
> 
> IO Summary:       8088 ops 8017.4 ops/s, (997/982 r/w) 155.6mb/s,    508us 
> cpu/op,   0.2ms

> I expected to see some higher numbers really...
> a simple "time mkfile 16g lala" gave me something like 280Mb/s.

mkfile isn't an especially realistic test for performance.  You'll note
that the fileserver workload is performing stats, deletes, closes,
reads, opens, and appends.  Mkfile is a write benchmark.  You might
consider trying the singlestreamwrite benchmark, if you're looking for
a single-threaded write performance test.

-j
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss

Reply via email to