From: Francis Cianfrocca <garbagecat10@...>
Date: 2008-02-10T21:19:35+09:00
Subject: Re: is lots of files with Threads faster?

------=_Part_2210_31215796.1202645982679
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

I basically gave up on optimizing hard-disk I/O long ago. (In
Ruby/EventMachine, I started adding an event-driven interface for disk
files, and will probably complete it someday, but initial profiling showed
relatively little benefit.)

A big part of the problem is that different machines have different
controller hardware, with a wide variance not only in raw performance, but
also in caching strategies and in the way they schedule the physical seeks.
Multispindle systems change the behavior yet again. You can develop on one
machine hoping to get some level of performance improvement, and find a
totally different behavior when you go to production.

On Feb 9, 2008 12:19 PM, James Tucker <jftucker@gmail.com> wrote:

> Take a look at the wide finder implementations on Tim Brays blog.
>
> It's quite interesting to see over there how little IO was a
> bottleneck. (Which seems to have been repeated a number of times here).
>
> Whilst the test environment is probably drastically different from
> your own, it might be worth looking at how some of those solutions
> solved the problem, and also give you some good reading on the topic.
>
> On 7 Feb 2008, at 20:21, Chris Richards wrote:
>
> > Im required to open 50+ files and parse the data in them.  WOuld using
> > multiple threads give me the best performance?  or is it best just
> > to do
> > it sequentially?
> >
> > THanks
> > Chris
> > --
> > Posted via http://www.ruby-forum.com/.
> >
>
>
>

------=_Part_2210_31215796.1202645982679--