maemo.org - Talk - View Single Post - [ANNOUNCE] CSSU-thumb thread

don_falcone	2012-06-13 , 10:03
Posts: 1,523 \| Thanked: 1,997 times \| Joined on Jul 2011 @ not your mom's FOSS basement	#90

Originally Posted by freemangordon

@don_falcone and others: could you try to build that iozone or whatever it is called and do some benchmarking

Attached. Build with MADDE (install-madde-0.7.48-linux-x86_64.sh) and their current source (iozone3_408.tar):

Code:

[user@host][current] mad -t fremantle-pr13 make linux-arm

Building iozone for Linux-arm

cc -c -O3 -Dunix -DHAVE_ANSIC_C -DASYNC_IO -DHAVE_PREAD \
        -DNAME='"linux-arm"' -DLINUX_ARM -DSHARED_MEM \
        -Dlinux -D_LARGEFILE64_SOURCE  iozone.c \
        -o iozone_linux-arm.o
iozone.c: In function 'main':
iozone.c:2636: warning: comparison is always false due to limited range of data type
iozone.c:2651: warning: comparison is always false due to limited range of data type
cc -c -O3 -Dunix -DHAVE_ANSIC_C -DASYNC_IO -D_LARGEFILE64_SOURCE \
        -DSHARED_MEM -Dlinux  libbif.c -o libbif.o
cc -c -O3 -Dunix -Dlinux -DHAVE_ANSIC_C -DASYNC_IO \
        -D_LARGEFILE64_SOURCE  libasync.c  -o libasync.o
make: Warning: File `libasync.o' has modification time 0.0015 s in the future

Building fileop for Linux-arm

gcc -Wall -c -O3  fileop.c -o fileop_linux-arm.o

Building the pit_server

cc -c   pit_server.c  -o pit_server.o 
cc -O3  iozone_linux-arm.o libbif.o libasync.o \
        -lrt -lpthread -o iozone
cc -O3 -Dlinux fileop_linux-arm.o -o fileop
cc -O3 -Dlinux pit_server.o -o pit_server
make: warning:  Clock skew detected.  Your build may be incomplete.

Had no time to play around much with it, though but it runs. EDIT: their help is here (Google Docs), and some example usage is explained here

EDIT 2:
Still digging through the examples and manual. A (albeit "temporary") command line would be:

Code:

### Multiple thread write test:
iozone -c -i0 -l 2 -u 2 -r 32k -s 1024k -+n -w -F /usr/tmp1 /opt/tmp2

### Multiple thread read test:
iozone -c -i1 -l 2 -u 2 -r 32k -s 1024k -+n -w -F /usr/tmp1 /opt/tmp2

-l indicates the minimum number of iozone processes that should be started: 2
-u indicates the maximum number of iozone processes that should be started: 2
-F should contain multiple values. i.e If we specify 2 in both -l and -u, we should have two filenames here. Please note that only the mount points need to exists. The file specified in the -F option doesn’t need to exists, as iozone will create this temporary file during the testing. In the above example, the mount points are /usr, and /opt. The files tmp1 and tmp2 will be automatically created by iozone for testing purpose.

As i dont know a good sector size etc. there's plenty of optimization room. note that option DIRECT IO (-I) seems not supported, as i got

Code:

Can not open temp file: iozone.tmp 
open: Invalid argument

Attached Files

iozone.gz (186.9 KB, 98 views)

Last edited by don_falcone; 2012-06-13 at 12:16.

Quote & Reply |

The Following 2 Users Say Thank You to don_falcone For This Useful Post:
misiak, szopin