[lkml]   [2002]   [Jun]   [20]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: ext3 performance bottleneck as the number of spindles gets large
On Thursday 20 June 2002 04:18 pm, Andrew Morton wrote:
> Yup.  I take it back - high ext3 lock contention happens on 2.5
> as well, which has block-highmem.  With heavy write traffic onto
> six disks, two controllers, six filesystems, four CPUs the machine
> spends about 40% of the time spinning on locks in fs/ext3/inode.c
> You're un dual CPU, so the contention is less.
> Not very nice.  But given that the longest spin time was some
> tens of milliseconds, with the average much lower, it shouldn't
> affect overall I/O throughput.

How could losing 40% of your CPU's to spin locks NOT spank your throughtput?
Can you copy your lockmeter data from its kernel_flag section? Id like to
see it.

> Possibly something else is happening.  Have you tested ext2?

No. We're attempting to see if we can scale to large numbers of spindles
with EXT3 at the moment. Perhaps we can effect positive changes to ext3
before giving up on it and moving to another Journaled FS.

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-03-22 13:26    [W:0.057 / U:0.040 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site