hmm, right now I'm wondering what kind of hardware is supposed to support a file IO of 1 millisecond I just did look through tomshardware enterprise hard drive charts ( http://www.tomshardware.com/charts/enterprise-hard-drive-charts-2010/Access-Time-Read-Average,2153.html ) and the fastest hard drive did need 5 milliseconds for actually accessing the file, so how should the io (which purely java/nativ) be faster then what the hardware actually is capable of doing? Though I might just now what warp like file-access hard drives are out there, so please forgive me :)
just my 2 cents, Achim 2011/11/14 ebinsingh <[email protected]> > Thanks a lot. This was what I was looking for. > > But the performance results were not what I was looking. > > To read a file, Camel is taking lot of time. I got the below numbers from > using Yourkit profiler. > > File of 10k records : 635 milliseconds > File of 20k records : 557 milliseconds > File of 40k records : 718 milliseconds > File of 80k records : 1408 milliseconds > File of 2k records : 34 milliseconds > > The code am using is > > from("file:/work_dir/camel_proj/data/input/mars") > .log("Starting to process big file: > ${header.CamelFileName}") > .split(body().tokenize("\n")).streaming() > > Is there a way to improve this. We are looking to use camel to read huge > number of files with varous amount of data each day. > Going by the above times, it's really far behind from what we are looking. > We are looking at reading file with 2k records in 1 millisecond. > > Please advise. > > Thanks & regards, > Ebe > > > -- > View this message in context: > http://camel.465427.n5.nabble.com/Type-Converters-Load-tp4982080p4991238.html > Sent from the Camel - Users mailing list archive at Nabble.com. > -- *Achim Nierbeck* Apache Karaf <http://karaf.apache.org/> Committer & PMC OPS4J Pax Web <http://wiki.ops4j.org/display/paxweb/Pax+Web/> Committer & Project Lead blog <http://notizblog.nierbeck.de/>
