Jeff Layton <jlayton@xxxxxxxxxx> wrote on 06/30/2008 08:56:54 PM:
> Recently I spent some time with others here at Red Hat looking
> at problems with nfs server performance. One thing we found was that
> there are some problems with multiple nfsd's. It seems like the I/O
> scheduling or something is fooled by the fact that sequential write
> calls are often handled by different nfsd's. This can negatively
> impact performance (I don't think we've tracked this down completely
> yet, however).
>
> Since you're just doing some single-threaded testing on the client
> side, it might be interesting to try running a single nfsd and testing
> performance with that. It might provide an interesting data point.
Works perfectly now!
With 64 nfsd's:
[root@localhost nfs]# ./perf
********** Testing on /nfs *************
Read Time: 50.6236 BW:29.63 MB/s
********** Testing on /local *************
Read Time: 38.3506 BW:39.11 MB/s
With 1 nfs'd:
[root@localhost nfs]# ./perf
********** Testing on /nfs *************
Read Time: 38.4760 BW:38.99 MB/s
********** Testing on /local *************
Read Time: 38.4874 BW:38.97 MB/s
I will try your other suggestions too.
I have to see what happens if I increase my processes. The real test is
DB2 using 300 connections. I will update when I run some more tests. But
thanks to everyone's help so far.
Regards,
- KK
--
To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
