Re: GFS Tuning - it's just slow, to slow for production

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi,

On Thu, 2010-03-04 at 09:12 -0600, Alan A wrote:
> Hello all - GFS2 is what we have deployed. It is fiber channel
> connection/HBA to HP XP SAN. 
> 
> What workload are you tuning for? The chances are that you'll do a lot
> better by adjusting the way in which the application(s) use the
> filesystem rather than tweeking any specific tuning parameters. What
> mount parameters are you using?
> 
> From /etc/fstab:
> /dev/mapper/vg_acct10-lv_acct10 /acct10 gfs
> rw,hostdata=jid=0:id=589826:first=1  0 0

The above says gfs not gfs2. I'd suggest using the noatime mount option
unless you really need atime support. Using atime is likely to make many
operations a lot slower.

The stats you've listed don't really tell us much. The question is what
the workload is, how the files/directories are layout out, and how they
are being accessed from each node,

Steve.


--
Linux-cluster mailing list
Linux-cluster@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/linux-cluster

[Index of Archives]     [Corosync Cluster Engine]     [GFS]     [Linux Virtualization]     [Centos Virtualization]     [Centos]     [Linux RAID]     [Fedora Users]     [Fedora SELinux]     [Big List of Linux Books]     [Yosemite Camping]

  Powered by Linux