A file reading benchmark
dawg at dawgfoto.de
Thu Feb 23 13:40:41 PST 2012
> On my machine (Mac OSX Lion), the Python code clocks around 1.2 seconds
> and the D code at a whopping 9.3 seconds. I looked around where the
> problem lies and sure enough the issue was with a slow loop in the
> generic I/O implementation of readln. The commit
> brings the speed of the test to 2.1 seconds. We could and should reduce
> that further with taking buffering in our own hands, but for now this is
> a good low-hanging fruit to pick.
Nice, I just got shocked yesterday by seeing that we call fgetc for every
those are usually macros and as we already maintain the per system
functions we might probably use the macro expansions.
More information about the Digitalmars-d