[haiku-commits] Re: r35129 - haiku/trunk/src/kits/tracker
- From: "Axel Dörfler" <axeld@xxxxxxxxxxxxxxxx>
- To: haiku-commits@xxxxxxxxxxxxx
- Date: Sun, 17 Jan 2010 21:19:15 +0100
Stephan Assmus <superstippi@xxxxxx> wrote:
> On 2010-01-17 at 20:00:35 [+0100], Axel Dörfler <axeld@xxxxxxxxxxxxxxxx>
> > wrote:
> > superstippi@xxxxxx wrote:
> > > Implemented display of current size/total size copied and current
> > > copy
> > > speed.
> > > It will begin to play after a short time (10 seconds).
> > Nice! But isn't 10 seconds much too long? Many operations won't
> > even take
> > that long, and I would still like to know the copy speed in those
> > cases -
> > it might already be more or less accurate much earlier (like 2
> > seconds I
> > would guess).
> Unfortunately, it's quite erratic with our current I/O scheduler.
> With 2
> seconds intervals, it may change for example between 70 MB/s and 7
> MB/s
> (same harddisk). Also, if the whole process lasts less than 10 seconds
> anyway, I don't really see the point in knowing how fast it is. In
> any
> case, it is possible to display it almost immediately by changing the
> algorithm slightly. I'll play with that. It will certainly be at the
> expense of raising false hopes in the beginning of a copy process...
> :-D
Thanks! I'd say we could keep it like this for a while, and if we then
decide waiting a bit more is the better idea after all, then we could
just change it back (or find something inbetween that works good
enough).
The I/O scheduler and most importantly, the write back strategy will
definitely change in the future, so that might bring more stable
numbers, too.
Bye,
Axel.
Other related posts:
