Christian Kellner wrote:
> This is acutally a dup of bug 64433 I filed a while ago. I am pretty
> sure it was fixed at some point but is now back again. The slow disk
> speed is damn annoying.
I have only tracked Feisty for about two weeks, and my drives performed
great with Edgy and 2.6.17. Actually took me a while to notice that
certain things were a little slower. One thing is much slower: I have
an XFS partition where I keep an Eclipse workspace. Eclipse (running
with Sun's Java 6 VM) writes a small file when the build process is
done, deletes it, and re-writes it about a dozen times (it's some
Eclipse metadata file about property indexes that I don't completely
understand--not part of my project). There was no apparent delay doing
this under 2.6.17/ahci, but with 2.6.20/piix it takes about 5 seconds
and (one) CPU is hammered the whole time. And Eclipse does incremental
compilation all the time (whenever you save a resource).
Java thread dumps during the big pause point to a thread waiting to
close the file stream or channel, which shouldn't take that long for a
200 byte file.
Christian Kellner wrote:
> This is acutally a dup of bug 64433 I filed a while ago. I am pretty
> sure it was fixed at some point but is now back again. The slow disk
> speed is damn annoying.
I have only tracked Feisty for about two weeks, and my drives performed
great with Edgy and 2.6.17. Actually took me a while to notice that
certain things were a little slower. One thing is much slower: I have
an XFS partition where I keep an Eclipse workspace. Eclipse (running
with Sun's Java 6 VM) writes a small file when the build process is
done, deletes it, and re-writes it about a dozen times (it's some
Eclipse metadata file about property indexes that I don't completely
understand--not part of my project). There was no apparent delay doing
this under 2.6.17/ahci, but with 2.6.20/piix it takes about 5 seconds
and (one) CPU is hammered the whole time. And Eclipse does incremental
compilation all the time (whenever you save a resource).
Java thread dumps during the big pause point to a thread waiting to
close the file stream or channel, which shouldn't take that long for a
200 byte file.
--
Shaw Terwilliger <`echo sterwill1io2nu | tr 12 @.`>