On Mon, Jun 30, 2008 at 6:10 AM, Krishna Kumar2 <krkumar2@xxxxxxxxxx> wrote: > Dean Hildebrand <seattleplus@xxxxxxxxx> wrote on 06/27/2008 11:36:28 PM: > >> One option might be to try using O_DIRECT if you are worried about >> memory (although I would read/write in at least 1 MB at a time). I >> would expect this to help at least a bit especially on reads. >> >> Also, check all the standard nfs tuning stuff, #nfsds, #rpc slots. >> Since with a loopback you effectively have no latency, you would want to >> ensure that neither the #nfsds or #rpc slots is a bottleneck (if either >> one is too low, you will have a problem). One way to reduce the # of >> requests and therefore require fewer nfsds/rpc_slots is to 'cat >> /proc/mounts' to see your wsize/rsize. Ensure your wsize/rsize is a >> decent size (~ 1MB). > > Number of nfsd: 64, and > sunrpc.transports = sunrpc.udp_slot_table_entries = 128 > sunrpc.tcp_slot_table_entries = 128 Interestingly, sometimes using a large number of slots can be detrimental to performance over loopback. Have you tried 32 and 64 as well as 128? Also, I seem to recall that you should have the same as or fewer slots on your clients than you have threads on your server. -- Chuck Lever -- 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
