Hey, hey.
Without divulging corporate secrets, does anyone have rules of thumb for some "normal" activity, how much NFS traffic if generated out the back of a beefy Web Client to a filer that is serving up the pages via NFS?
Rough feels and spreads is all I was curious about...
I'm not sure I have ready access to a Web front end/filer back end setup that would be meaningful...
Mostly I'm curious.
(The number just thrown out, with no justification, was
Each "hit" results in 5 NFS operations.
I'm sitting here pounding my head trying to understand the "5".
V3 might yield:
LOOKUP ACCESS READ
Per page hit. Is average object size 8 - 12KB? So one read on V3? I assume Apache front ends are not "browsing" they're firing names at the filer. Etc.
I thought it an interesting question.
What does the op mix look like for a filer backing a Web host? (I've seen the mix, I guess I was never startled enough to remember, seemed boring with lots of LOOKUPs, 10% READs, 5 - 8% WRITEs?).
beepy