On Mon, 2002-03-04 at 09:41, Jose Celestino wrote:
We are currently experiencing some heavy load on a filer serving as storage to a webmail farm:
Which model filer?
The filer volume webmail:
FILER> df Filesystem kbytes used avail capacity Mounted on /vol/webmail/ 406736736 383407488 23329248 94% /vol/webmail/ /vol/webmail/.snapshot 101684180 0 101684180 0% /vol/webmail/.snapshot
Looks like you have the snapshot reserve set to 20% and dont use it. You should recover that space. The more space you give the filer on the volume, the better ;)
The getattr seems way too big and this may point to a bad caching on the frontends. But could this bring the CPU to 100% most of the time? Could this be a wafl issue related with the low available space on the volume?
Are the clients doing v2 or v3 NFS mounts? Old data (from a previous life) suggests that for mail and news applications v2 edges out v3. From the looks of it you have both types of access going on.
Any ideas to help optimize the performance in this scenario? Any ideas are welcome.
It looks (from the 22 second snapshot of sysstat) that the writes are when the filer is getting pushed. Some things to look at as possible improvements (some require more work than others):
- what do the raid groups look like? smaller groups may help the writes - if snapshots are disabled (which makes sese for a mail filer), then recover the snap reserve space. - how much read cache do you have in the filer? Max it out. - it looks like there is a fair ammount of network activity; you might want to enable a vif or upgrade to gige. - what OS do the clients run? some have better nfs performance than others. Perhaps there are newer versions out.
You might also be at the breaking point for the filer (but I think you can get a bit more out of it by making some of the changes listed above).
At what rate do you add mailboxes and grow the data on the filer?
alexei