I am testing an application which to a lot of link/unlink
server is a NetApp filer, client is linux 2.4.19+nfs patches.
under load it seems that the unlink call is very long when all over calls
response time seems to be OK.
is there any problems with the unlink code ?
thanks
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
NFS maillist - [email protected]
https://lists.sourceforge.net/lists/listinfo/nfs
link RPCs can be very large (much larger than wsize, for instance).
if you use UDP and your network drops lots of packets, large link
requests will probably require several retransmissions to complete.
enlarge your transport socket buffer size on the client (see FAQ)
and/or try NFS over TCP. also examine your network to see if it
is clean, and is working optimally. if your client is attached
via a more slow link than your server, that can be the source of
bursty packet loss.
> -----Original Message-----
> From: Brasseur Val=E9ry [mailto:[email protected]]
> Sent: Monday, August 12, 2002 8:09 AM
> To: [email protected]
> Subject: [NFS] nfs unlink perf !
>=20
>=20
> I am testing an application which to a lot of link/unlink
>=20
> server is a NetApp filer, client is linux 2.4.19+nfs patches.
>=20
> under load it seems that the unlink call is very long when=20
> all over calls
> response time seems to be OK.
> is there any problems with the unlink code ?
>=20
> thanks
>=20
>=20
>=20
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> _______________________________________________
> NFS maillist - [email protected]
> https://lists.sourceforge.net/lists/listinfo/nfs
>=20
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
NFS maillist - [email protected]
https://lists.sourceforge.net/lists/listinfo/nfs
>>>>> " " =3D=3D Brasseur Val=E9ry <[email protected]> writes:
> I am testing an application which to a lot of link/unlink
> server is a NetApp filer, client is linux 2.4.19+nfs patches.
> under load it seems that the unlink call is very long when all
> over calls response time seems to be OK. is there any problems
> with the unlink code ?
There should be no problems, but it depends on what type of test you
are doing...
The NFS protocol has to work around some nasty compatibility problems
w.r.t. the POSIX expected behaviour of unlink. In particular, POSIX
allows you to do
open(file);
write(file);
unlink(file);
read(file);
close(file);
i.e. to unlink an open file...
In order for the above to work with NFS, one can't immediately unlink
the file when it is open(). Instead, NFS does a 'sillyrename': it
renames the file to something of the form .nfsXXXXX (where XXXX is
some number) and then performs the unlink when the 'close()' has been
performed.
Would this suffice to explain your 'bad performance'?
Cheers,
Trond
-------------------------------------------------------
This sf.net email is sponsored by: Dice - The leading online job board
for high-tech professionals. Search and apply for tech jobs today!
http://seeker.dice.com/seeker.epl?rel_code=31
_______________________________________________
NFS maillist - [email protected]
https://lists.sourceforge.net/lists/listinfo/nfs