Performance mustek 600 II N

Henning Meier-Geinitz (henningmg@gmx.de)
Mon, 13 Apr 1998 22:26:26 +0200

I did some tests with the mustek 600 II N scanner, sane 0.72 and
Windows. A page was scanned with a geometry of 22 X 10 cm. I used
Gimp/Xscanimage on Linux and the supplied driver and painting program
with Windows 95. The time is measured between pressing the "scan"
button and displaying the picture [in seconds].

"buffer" ist the buffer size in kB used in mustek.c (reader_process).

sane windows
color buffer: 32 buffer: 256

100 dpi 18 18 21
200 dpi 31 34 36
300 dpi 48 48 53

grayscale

100 dpi 11 11 13
200 dpi 18 12 13
300 dpi 40 26 19

lineart

100 dpi 10 10 11
200 dpi 12 11 12
300 dpi 15 13 13
600 dpi 42 41 24

A buffesize bigger then 256 kB doesn't change anything. A bigger
buffer reduces backtracking in grayscale and therefor reduces scanning
time.

Windows is faster with higher resolutions in grayscale and lineart
mode, it nearly doesn't backtrack there. It seems to be very fast at
reading data from the scanner, perhaps that part can be optimized in
sane (sanei_ab306.c/mustek.c). Windows seems to be slower in doing the
line-distance correction.

However, with linux and sane I can do other things while scanning,
Windows is stuck totally.

600 dpi in grayscale and color doesnt't work here with sane correctly,
so I didn't test it.

Ciao, Henning

--
Source code, list archive, and docs: http://www.mostang.com/sane/
To unsubscribe: echo unsubscribe sane-devel | mail majordomo@mostang.com