On Saturday, 24 December 2016 at 17:52:04 UTC, Chris Wright wrote:
The minimum isn't terribly useful because it gets to the point
of testing the process scheduler and IO more than the compiler.
If we want numbers that we can trust on the low end, we'll need
to put timing information into the compiler, maybe control for
IO by using a ramfs, that sort of thing.
As a good approximation you can use a profile build of dmd.
It will give you a breakdown of how long the individual functions
took.
Due to the way the profiling works, it does homogenize the values
a bit.
Files are not streamed into dmd, it reads them as one Block.
Therefore there is no need for a ramfs.
