On Wed, 5 Jul 2017, at 17:44, P.O. Jonsson wrote: > To make a „baseline“ test I wrote a C program that is doing roughly the > same as the oorexx test. Reading in 1 Million lines in C byte by byte > takes 1.3 seconds, ooRexx 4.2 clocks in at 2.7 seconds (which is GREAT)
I think you may need to be wary of times like these, simply because after the first program (whether it's a C one or an ooREXX one) has executed, the test data might be being cached in the disk controller or I/O buffers in RAM so all following read tests might be faster than they would have been had they been the first one. I don't know how to get around that, except perhaps by generating multiple test files for subsequent programs to read then doing some colossal amount of other I/O so that no cache or buffer contains the values you're about to read. -- Jeremy Nicoll - my opinions are my own. ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Oorexx-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/oorexx-devel
