Skip to contentSkip to conversation

Performance problem

DISCUSSION Nicolas Brainez 2 participants 2 messages May 15, 2002

Subsystems (2)
lore
Share & tools
lore
#0 lore raw

OK, thanks for all your response!

I've tried the following:

- Change the NIC (old was rtl8139, new is AMD pcnet32): no changes
- Mount nfs in local: no problem
- Pinging server with 8192 bytes: high packet loss ! (between 30 & 90%)

It's maybe no more an nfs problem but, in my LAN the mtu are @ 1500 on every machine, and there's no router between server and workstations, some tips will be appreciated :-).

--
Nicolas Brainez

_______________________________________________________________

Have big pipes? SourceForge.net is looking for download mirrors. We supply the hardware. You get the recognition. Email Us: [email protected]
_______________________________________________
NFS maillist - [email protected]
https://lists.sourceforge.net/lists/listinfo/nfs

#1 lore raw
Quoted 1 line · Nicolas Brainez

- Change the NIC (old was rtl8139, new is AMD pcnet32): no changes

The rtl8139 is a terrible NIC. It doesn't seem to work under high load under any OS.

Quoted 1 line

- Pinging server with 8192 bytes: high packet loss ! (between 30 & 90%)

Well, there's your problem. As you could imagine, NFS with 8k packets won't work so well, but you won't notice for telnet.

You have 2 choices to cover up the problem:

1) Use NFS over TCP.
2) Use NFS with UDP and 1k packets.

As for what the underlying problem is, I don't really know. I would follow up by using "netperf" or another TCP-related test to see if the TCP bandwidth is acceptable. If it is, then you can not fix it...

greg

_______________________________________________________________

Have big pipes? SourceForge.net is looking for download mirrors. We supply the hardware. You get the recognition. Email Us: [email protected]
_______________________________________________
NFS maillist - [email protected]
https://lists.sourceforge.net/lists/listinfo/nfs