We only use our filers for CIFS (so this may be completely inapplicable to you)
1. Cache age! Mainly because when I have seen filers that are worked to death, that's the value that tends to react to it (though CP there are a lot of secondary metrics to support that).
2. As mentioned by someone else...the magic metric is how badly the users are bitching. That being a little "rubbery" we also check cache age, cp type, disk utilisation, cpu usage, Ops/sec and network traffic to determine if anything's bottlenecking.
-----Original Message----- From: owner-toasters@mathworks.com [mailto:owner-toasters@mathworks.com] On Behalf Of Rohit Sent: Wednesday, 15 November 2006 9:59 PM To: toasters@mathworks.com Subject: Measuring Filer Performance
Hi Folks
I had some open questions and i hope you'll help me answer them based on your experience.
1. If you just had a single metric to determine filer performance what would it be ? Would it be CPU usage, throughput, latency, IOPS..or anything else ?
2. At your place, what metrics do you use to determine if a filer is still good enough not to worry about ?
thanks rohit
------------------------------------------------------------------------ -- Refinance & Home Equity Loan Quotes Low credit score? Old Merchants can help. Get a quote in 2 easy steps! http://tagline.bidsystem.com/fc/BgLEQfI7zNZsu5fZHhXyj0UMjSNzY6ZfSaWC/
"This e-mail and any attachments to it (the "Communication") is, unless otherwise stated, confidential, may contain copyright material and is for the use only of the intended recipient. If you receive the Communication in error, please notify the sender immediately by return e-mail, delete the Communication and the return e-mail, and do not read, copy, retransmit or otherwise deal with it. Any views expressed in the Communication are those of the individual sender only, unless expressly stated to be those of Australia and New Zealand Banking Group Limited ABN 11 005 357 522, or any of its related entities including ANZ National Bank Limited (together "ANZ"). ANZ does not accept liability in connection with the integrity of or errors in the Communication, computer virus, data corruption, interference or delay arising from or in respect of the Communication."