On Wed, Apr 11, 2001 at 06:29:30PM -0700, Anton Blanchard wrote:
> > This patch provides a very good performance improvement in file
> > descriptor management for SMP linux kernel on a 4-way machine with the
> > expectation of even higher gains on higher end machines. The patch uses the
> > read-copy-update mechanism for Linux, published earlier at the sourceforge
> > site under Linux Scalablity Effort project.
> > http://lse.sourceforge.net/locking/rclock.html.
> Good stuff!
> It would be interesting to try a filesystem benchmark such as dbench. On
> a quad PPC fget was chewing up more than its fair share of cpu time.
Thank you for your suggestion. I tried dbench for on a 4-way PIII Xeon box, with
1MB L2 Cache and 1GB of RAM. I ran it on 8 GB ext2 partition with Adaptec 7896
SCSI controller. I ran "dbench 100" and "dbench 200" for five times and took the
average of the throughput and found that for
Base (2.4.2) -
100 Average Throughput = 39.628 MB/sec
200 Average Throughput = 22.792 MB/sec
Base + files_struct patch -
100 Average Throughput = 39.874 MB/sec
200 Average Throughput = 23.174 MB/sec
I found this value quite less than the one present in the README distributed
with dbench tarball. I think the numbers in the README were for a similar
machine but with 2.2.9 kernel.
As you can see the performance with files_struct patch is almost same as base.
I feel I am hitting some bottleneck other than fget() in both base and the
patched versions. I think atleast for base version I should get similar numbers
as mentions in the README for similar configuration. Though I intend to do some
profiling to look into this but it will be helpfull if you can tell me if there
is some known thing regarding this.
I am copying this to Andrew also, if he can also help. Also if you have some
dbench numbers from 2.4.x kernel, please let me have a look into those also.
-- Maneesh Soni <firstname.lastname@example.org> IBM Linux Technology Center, IBM Software Lab, Bangalore, India - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to email@example.com More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Sun Apr 15 2001 - 21:00:19 EST