Comment 30 for bug 1006446

Revision history for this message
perpetualrabbit (perpetualrabbit) wrote :

@Christoph Bartoschek
Any load over the number of cpu cores (X) is not acceptable.
You have X camels. Each camel can carry one sack of flour. If you want to move more than X sacks of flour, some camels will have to make second trips.

That is how `load´ works, right? Any load over X will make the performance collapse in some way. Throughput will level off or even decrease. You get time-outs or at least increased latency.

Since you have 8 cores, even load 10 is simply way too high. 2x4 cores, 48 GB and gigabit? If these are only nfs servers, and for only 20 clients, they are way too powerful. You could serve 500 to 1000 clients on that. You probably run other service too? Web, mail etc?

Of course there is no reason that the nfs daemons should cause so much cpu usage. 10.04 didn't, so why should that suddenly happen now?
Your load should normally be far below one, for an nfs server.

As far as I know, there haven't been major changes in linux's NFS stack in the last 3 -4 years, but there have been in the storage layer, such as IO scheduling. The fact that changing the scheduler makes the load go from 100 to 10 is telling.