Linux LVM users
 help / color / mirror / Atom feed
From: Austin Gonyou <austin@coremetrics.com>
To: linux-lvm@sistina.com
Subject: RE: [linux-lvm] LVM System
Date: Mon Mar  4 18:12:02 2002	[thread overview]
Message-ID: <1015287114.24628.0.camel@UberGeek> (raw)
In-Reply-To: <NBBBKLKHMJHIJLHOGAOJCEFPJFAA.steve.wray@paradise.net.nz>

Hmm..that could be so, but I'm not sure if it's JUST xfs or if it's
XFS/LVM. My largefile performance is excellent, as is my small file
perfromance. 

On Mon, 2002-03-04 at 18:01, Steve Wray wrote:
> Well, thats possible. The best thing to do is run
> benchmarks (I like iozone) on the proposed
> system and see what works best.
> The tests I did were just on small filesystems (1G volumes,
> 64M, 128M and 196M RAM). Filesizes I tested were only
> up to 500M or so.
> I found that while most tested filesystems (reiser, XFS,
> ext3 and vfat) did drop off in performance as filesize
> increased, XFS dropped off the most rapidly in that
> dimension. ext3 was the most stable (in performance as filesize
> increased), though its small filesize performance was the worst.
> XFS looked like kinda the opposite!
> :)
> Reiser had the worst write performance of all of them,
> but admirable read.
> 
> YMMV.
> 
> 
> 
> > -----Original Message-----
> > From: linux-lvm-admin@sistina.com
> [mailto:linux-lvm-admin@sistina.com]On
> > Behalf Of Anthony W. Marino
> > Sent: Tuesday, 5 March 2002 12:50 p.m.
> > To: linux-lvm@sistina.com; Steve Wray
> > Subject: Re: [linux-lvm] LVM System
> > 
> > 
> > On Monday 04 March 2002 06:39 pm, Steve Wray wrote:
> > > I'd recommend ext3 with data journalling for sensitive
> > > filesystems. Its slower than XFS but (seems to) scale better with
> > > striping and large files. XFS performance (seems to) fall off
> > > very rapidly as file size exceeds buffer size.
> > >
> > > XFS only journals metadata. So on event of a crash,
> > > the filesystem structure will (likely) be sound, but theres
> > > no guarantee that the data blocks will be uncorrupted!!!
> > >
> > > XFS is very nice tho, in that volumes and filesystems can
> > > be grown with no downtime at all (without even unmounting).
> > >
> > > You might want to do some benchmarking before committing
> > > to a build (thats recently saved my butt actually).
> > 
> > It was recommended to me that all large file systems have best 
> > performance 
> > with XFS.
> > 
> > > > -----Original Message-----
> > > > From: linux-lvm-admin@sistina.com 
> > [mailto:linux-lvm-admin@sistina.com]On
> > > > Behalf Of Anthony W. Marino
> > > > Sent: Tuesday, 5 March 2002 10:39 a.m.
> > > > To: linux-lvm@sistina.com
> > > > Subject: [linux-lvm] LVM System
> > > >
> > > >
> > > > Any thoughts or articles that would be usefull in determining 
> > the quality
> > > > on the following combination would be greatly appreciated:
> > > >
> > > > LVM 1.x
> > > > 3Ware 7800 Raid Controller
> > > > Maxtor 40GB harddrives
> > > > XFS Journalling FS
> > > > SuSE 2.4.18+ Linux
> > > >
> > > >
> > > > Thank You,
> > > > Anthony
> > > >
> > > > _______________________________________________
> > > > linux-lvm mailing list
> > > > linux-lvm@sistina.com
> > > > http://lists.sistina.com/mailman/listinfo/linux-lvm
> > > > read the LVM HOW-TO at http://www.sistina.com/lvm/Pages/howto.html
> > >
> > > _______________________________________________
> > > linux-lvm mailing list
> > > linux-lvm@sistina.com
> > > http://lists.sistina.com/mailman/listinfo/linux-lvm
> > > read the LVM HOW-TO at http://www.sistina.com/lvm/Pages/howto.html
> > 
> > _______________________________________________
> > linux-lvm mailing list
> > linux-lvm@sistina.com
> > http://lists.sistina.com/mailman/listinfo/linux-lvm
> > read the LVM HOW-TO at http://www.sistina.com/lvm/Pages/howto.html
> > 
> 
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@sistina.com
> http://lists.sistina.com/mailman/listinfo/linux-lvm
> read the LVM HOW-TO at http://www.sistina.com/lvm/Pages/howto.html
-- 
Austin Gonyou
Systems Architect, CCNA
Coremetrics, Inc.
Phone: 512-698-7250
email: austin@coremetrics.com

"It is the part of a good shepherd to shear his flock, not to skin it."
Latin Proverb

  reply	other threads:[~2002-03-04 18:12 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-04 15:39 [linux-lvm] LVM System Anthony W. Marino
2002-03-04 15:51 ` lembark
2002-03-04 16:03   ` Anthony W. Marino
2002-03-04 16:00 ` Theo Van Dinter
2002-03-04 16:07   ` Anthony W. Marino
2002-03-04 16:11     ` Anthony W. Marino
2002-03-04 16:27     ` Theo Van Dinter
2002-03-04 16:39       ` Anthony W. Marino
2002-03-04 21:21         ` Theo Van Dinter
2002-03-04 21:36           ` Anthony W. Marino
2002-03-04 16:12   ` Anthony W. Marino
2002-03-04 17:39 ` Steve Wray
2002-03-04 17:50   ` Anthony W. Marino
2002-03-04 18:01     ` Steve Wray
2002-03-04 18:12       ` Austin Gonyou [this message]
2002-03-04 18:23         ` Steve Wray
2002-03-04 18:32           ` Austin Gonyou
2002-03-04 18:38             ` Steve Wray
2002-03-04 18:46             ` Goetz Bock
2002-03-04 19:58               ` Petro
2002-03-04 17:53   ` Austin Gonyou
2002-03-04 18:18     ` Anthony W. Marino
2002-03-04 18:39 ` Goetz Bock
2002-03-04 18:47   ` Anthony W. Marino
2002-03-04 18:51     ` Goetz Bock

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1015287114.24628.0.camel@UberGeek \
    --to=austin@coremetrics.com \
    --cc=linux-lvm@sistina.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox