Messages in this thread | | | From | "Griffiths, Richard A" <> | Subject | RE: ext3 performance bottleneck as the number of spindles gets la rge | Date | Thu, 20 Jun 2002 13:45:22 -0700 |
| |
No. The platform group is set on a journaling file system. They had already run a comparison of the ones available and based on their criteria, ext3 was the best choice. Based on the lockmeter data, it does look as though the scaling is trapped behind the BKL.
Richard
-----Original Message----- From: Andrew Morton [mailto:akpm@zip.com.au] Sent: Thursday, June 20, 2002 1:19 PM To: Griffiths, Richard A Cc: 'Jens Axboe'; mgross@unix-os.sc.intel.com; Linux Kernel Mailing List; lse-tech@lists.sourceforge.net Subject: Re: ext3 performance bottleneck as the number of spindles gets large
"Griffiths, Richard A" wrote: > > We ran without highmem enabled so the Kernel only saw 1GB of memory. >
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.
Possibly something else is happening. Have you tested ext2? - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |