Kevin,
For Solaris, look at http://docs.sun.com/ab2/coll.707.1/SOLTUNEPARAMREF/@Ab2PageView/8183?DwebQuery=nfs+OR+tuning&oqt=nfs+tuning&Ab2Lang=C&Ab2Enc=iso-8859-1
This is from docs.sun.com, Solaris Tunable Parameters Collection , Solaris Tunable Parameters Reference Manual
The default of the kernel flag nfs:nfs3_lookup_neg_cache is 1 - DO cache negative lookups on mounted NFS servers.
Hope it helps, Eyal.
---------------------------------------------------------------------- eTraitel - I'm the new eBuzzword around !!! ---------------------------------------------------------------------- Eyal Traitel - Filer Escalation Engineer CNA, MCSE, CSA, LCA, NetApp CA
Network Appliance BV Holland Office Center Kruisweg 799b 2132 NG, Hoofddorp The Netherlands Office: +31 23 567 9685 Cellular: +31 6 5497 2568 Email: eyal@netapp.com ---------------------------------------------------------------------- Get answers NOW! - NetApp On the Web - http://now.netapp.com ----------------------------------------------------------------------
-----Original Message----- From: kevin graham [mailto:kgraham@dotnetdotcom.org] Sent: Sunday, April 08, 2001 5:00 AM To: toasters@mathworks.com Subject: reducing getattr's
Slightly OT, as it isn't directly netapp related, but does anyone know of a way to test if a file exists in Solaris besides a full-fledged stat() or attempting an open? I'm looking through web server stats, and I noticed I'm spending most of my nfs time doing getattrs, which I presume map back to stats that (mostly) test for existance.
It strikes me that a getattr is rather painful in contrast to a lookup, but I have no idea how (or if) if the lesser can be forced.
I've toyed with the idea of increasing actimeo and friends up, but am not sure of all the caveats of doing so (namely, are negative entries cached? I'm thinking along the lines of DNS's NXDOMAIN cachine semantics .. false positives would be OK, but the false negatives would be baaad).
Ideas?
Thanks.
..kg..