A
Andrey Kuznetsov
see http://uio.imagero.com and http://uio.imagero.com/performance.html
uio makes buffering for you (so you always have the best performance),
and makes io handling more comfortable - for example with reading/writing of
primitive arrays.
If you use IO or NIO incorrect (i.e. calls readInt() million times)
then you can see that UIO gives you 100 time better performance.
uio can't beat IO or NIO if you use them correct.I managed to read the file and iterate thru it in 4 byte chunks in about
60ms using NIO and a DirectByteBuffer. Do you think UIO can beat this?![]()
uio makes buffering for you (so you always have the best performance),
and makes io handling more comfortable - for example with reading/writing of
primitive arrays.
If you use IO or NIO incorrect (i.e. calls readInt() million times)
then you can see that UIO gives you 100 time better performance.