Thanks a lot gentlemen for all your suggestions... I played a little bit with the rsize and wsize options for the nfs clients and I made some test on the network speed with some dd commands.
The best results for the clients were obtained with rw,soft,rsize=8192,wsize=8192 To test the writing speed, I execute the following command several time on the client in order to have an average. The /home is mounted through nfs. >time dd if=/dev/zero of=/home/testfile bs=16k count count=4096 This command creates a 64Mo file containing only 0 on the /home, at the speed of 70 MB/sec. This is not exceptional indeed... Network speed remains slow despite the rsize and wsize options and the required time to link my object files is still dramatically high! To test the reading speed (the /tmp mounted locally on the nfs client): >time dd if=/home/testfile of=/tmp/tesfile bs=16k This gave a speed of 295 MB/sec, much more compared to the writing speed. Can this difference be explained and corrected somehow? I would also like to mention that I did not have this slow linking problem with my former Linux distribution (Mandriva 2006), and configured with the same nfs options. So there still must be a problem with my SuSE network configuration somewhere. Anyway, I tried to compile and link my object files locally on a nfs client, keeping my source code on the /home mounted through nfs. The results is quite nice! Now, the linking process is straightforward (less than 1 second) and I do not have time to go and take a coffee any more as before ;-) I will adopt this solution and continue with the "rw,soft,rsize=8192,wsize=8192" options for the nfs clients. Thanks a lot again... I hope I will be able to help you one day as well... Cheers, Michel -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
