lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Engels" <>
Subject RE: NioFile cache performance
Date Fri, 09 Dec 2005 16:27:28 GMT
As stated in a previous email - good idea.

All of the code and testcases were attached to the original email.

The testcases were the answer to a request for such (at least a month ago if
not longer).

-----Original Message-----
From: DM Smith []
Sent: Friday, December 09, 2005 7:07 AM
Subject: Re: NioFile cache performance

John Haxby wrote:

> Robert Engels wrote:
>> Using a 4mb file (so I could be "guarantee" the disk data would be in
>> the OS cache as well), the test shows the following results.
> Which OS?   If it's Linux, what kernel version and distro?   What
> hardware (disk type, controller etc).
> It's important to know: I/O (and caching) is very different between
> Linux 2.4 and 2.6.   The choice of I/O scheduler can also make a
> significant difference on 2.6, depending on the workload.   The type
> of disk and its controller is also important -- and when you get
> really picky, the mobo model number.
> I don't dispute your finding for a second, but it would be good to run
> the same test on other platforms to get comparative data: not least
> because you can get the kind of I/O time improvement you're seeing on
> some workloads on different versions of the Linux kernel.

I think that the results were informative from a comparative basis on a
single machine. It compared different techniques and showed their
relative performance on that machine.

I also agree that the architecture of the machine can play an important
part in how code performs. I wrote a piece of software that ran well on
a 4-way, massive raid configuration, with gobs of ram only to have it
re-targeted to a 1-way, small ram box, where it had to be rewritten to
run at all.

Perhaps, it would be good to establish guidelines for reporting
performance, including the posting of test data and test code.

This may encourage others to download the data and code, perform the
test and report the results.

To unsubscribe, e-mail:
For additional commands, e-mail:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message