Re: nfs performance at high loads

David Mansfield (lkml@dm.ultramaster.com)
Wed, 25 Apr 2001 16:56:19 -0400


Kapish K wrote:
>
> Hello,
> I had sent in a note on nfs performance issues some time back,
> and Mark Hemment had been kind enough to point out to the
> zerocopy networking patch. Well, we tried with it, and it does
> seem to have some improvement, but it seems to have screwed up
> nfs performance a bit, because we see a LOT of rpc failures for
> all kinds of calls, starting from lookup, to read and writes.
> Could this possibly be triggered by this patch ( picked up from
> davem's site for 2.4.0 ).
> On the other hand, we do plan to migrate to 2.4.2. Can somebody
> update me or provide pointers to info. as to whether we can
> expect some of these problems have been resolved in 2.4.2? We
> should soon be testing on 2.4.2
> Thanks
>

While I'm not an expert hacker or anything, I can tell you for sure,
that even 2.4.2 is full of really system crippling bugs. You need to
track the current kernels. All of the 2.4.x series should be
compatible, in other words, you should upgrade as soon as possible to
the latest stable kernel. Currently, that's 2.4.3 (not 2.4.2). And
even 2.4.3 has many known bugs that are capable of 1) destroying
performance and 2) destroying filesystems.

At the very least, you should upgrade to 2.4.3, but better yet would be
to upgrade to the 2.4.4 when it comes out (soon?), or even the 2.4.4-pre
patch since it has the zero copy networking patch already included, as
well as fixes for bugs that could corrupt your filesystems. The zero
copy patch as it existed for 2.4.0 was also buggy in itself, so that
would explain some of your extended problems.

Really, 2.4.0 is a 'horrible' kernel to be running, as it is missing an
enormous amount of performance fixes, and bug fixes.

David

-- 
David Mansfield                                           (718) 963-2020
david@ultramaster.com
Ultramaster Group, LLC                               www.ultramaster.com
-
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/