On 20 Mar 2013 05:33, "nick black" <email@example.com> wrote:
> I am testing on two machines, a Core i7 2600K quadcore with HyperThreading,
> overclocked to 5.0GHz ("skynet"), and a Core 2 Duo 6600 at stock 2.4GHz
> ("recombinator"). I ran each mode 10 times with each binary on each machine,
> without interleaving. As the working set of each binary can be kept easily
> within page cache on either machine, these tests probably do not reflect true
> disk i/o. Disk I/O would be expected to only help RAPTORIAL relative to
> apt-show-versions, given that RAPTORIAL will issue its disk reads in parallel,
> rather than sequentially, and that they can all fit in page cache. These tests
> use RAPTORIAL 0.1.5, Libblossom 1.2.2, and the native SprezzOS APT databases of
> the machines.
There is no need to guess... Us the drop-cache proc file to trigger I/O.