| To: | "Steve Lord" <lord@xxxxxxx> |
|---|---|
| Subject: | Odp: Benchmarking ReiserFS, ext2, XFS |
| From: | "Blizbor (i)" <tb670725@xxxxxx> |
| Date: | Wed, 16 May 2001 18:39:47 +0200 |
| Cc: | <reiserfs-list@xxxxxxxxxxx>, "Linux XFS Mailing List" <linux-xfs@xxxxxxxxxxx> |
| References: | <Pine.LNX.4.21.0105161929390.1579-100000@xxxxxxxxxxxxxxxxxxx> <200105161451.f4GEpcj17003@xxxxxxxxxxxxxxxxxxxx> |
| Sender: | owner-linux-xfs@xxxxxxxxxxx |
----- Original Message -----
From: Steve Lord <lord@xxxxxxx>
> p.s. For the filesystem mkfs and mount part of mongo.pl I would recommend
> this:
>
> if ( $FILESYSTEM eq "xfs" ) {
> system("mkfs -t xfs -f -l size=16384b $DEVICE") ;
> system("mount -o logbufs=4,osyncisdsync $DEVICE $TESTDIR") ;
> }
Could these mount options can be also applied on production server ?
(i.e. mail, web and sql db server ?)
Is there possibility to limit memory used for disk/file cacheing ?
How mkfs.xfs calculates values for agcount and agsize ?
(I have spent some time trying to find apropriate "-l SIZE"
for each created fs)
On 15GB filesystem, did it makes big difference that it was created
with "-l" value twice as you suggest ?
Am I wrong thinking that noatime, nodiratime mount options also are
tweaking XFS performance (as for ext2fs) ? (I dont need these info at
all).
Regards,
Blizbor
|
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: Benchmarking ReiserFS, ext2, XFS, Austin Gonyou |
|---|---|
| Next by Date: | Re: vmware file locking problem:, pac |
| Previous by Thread: | Re[2]: Benchmarking ReiserFS, ext2, XFS, Austin Gonyou |
| Next by Thread: | Re: Odp: Benchmarking ReiserFS, ext2, XFS, Steve Lord |
| Indexes: | [Date] [Thread] [Top] [All Lists] |