80K is a lot of NFS ops to say the least. I wasn't awareYou may be at the limits of the device, but we won't know for sure until we see a few statistics.

Questions;

What is disk utilization during this period? I assume your sysstat is indicating at least one disk is at 100%

What size raid groups do you have on your volumes?

Please capture a statit output? Rsh <filer> "priv set advanced;statit -b" , leave for a period while the utilization is known to be high. Rsh <filer> "priv set advanced;statit -e" > output.log (capturing output to a file).

Let have a look at that output and see if you are bound on one or a few disks in a raid group, or whether you are just asking too much of the filer. There are a few other things in the statit that will be useful.

You may have to look at splitting the workload across volumes or even into other filers.

--Aaron

-----Original Message----- From: cisco joe [mailto:ciscojoe305@yahoo.com] Sent: Tuesday, 30 November 2004 2:45 AM To: toasters@mathworks.com Subject: Simulation jobs peaking filer CPU & CP

All,

We have some issues with LSF simulation jobs writing to filers(FAS960) ..

Filer's CPU peaking to 100% and NFS goes beyond 80K and CP back to back happening when users executes LSF regress simulations jobs...These jobs has heavy writes to filer and even read also high..

Because of this huge writes filer is going to hung state where simple ls or df from NFS is hanging ..Even telnet or rsh to filer will take long time ...

If anybody has any workaround pls let me know

Any suggestions is highly helpful

Thanks Joe

__________________________________ Do you Yahoo!? Take Yahoo! Mail with you! Get it on your mobile phone. http://mobile.yahoo.com/maildemo

************** IMPORTANT MESSAGE ************** This e-mail message is intended only for the addressee(s) and contains information which may be confidential. If you are not the intended recipient please advise the sender by return email, do not use or disclose the contents, and delete the message and any attachments from your system. Unless specifically indicated, this email does not constitute formal advice or commitment by the sender or the Commonwealth Bank of Australia (ABN 48 123 123 124) or its subsidiaries. We can be contacted through our web site: commbank.com.au. If you no longer wish to receive commercial electronic messages from us, please reply to this e-mail by typing Unsubscribe in the subject line. ***************************************************************