From: Andreas Dilger <adilger@turbolinux.com>
To: Roberto Fichera <kernel@tekno-soft.it>
Cc: Jakob Østergaard <jakob@unthought.net>, linux-kernel@vger.kernel.org
Subject: Re: Ext2 & Performances
Date: Tue, 21 Nov 2000 11:32:13 -0700 (MST) [thread overview]
Message-ID: <200011211832.eALIWDD20416@webber.adilger.net> (raw)
In-Reply-To: <4.3.2.7.2.20001121190033.00d23bc0@mail.tekno-soft.it> "from Roberto Fichera at Nov 21, 2000 07:16:19 pm"
Roberto Fichera writes:
> I'm configuring a Compaq ML350 2x800PIII, 1Gb RAM, 5x36Gb UWS3 RAID 5
> with Smart Array 4300, as database SQL server. So I need to chose
> between a single partition of 130Gb or multiple small partitions,
> depending by the performance.
It is usually better to have multiple small partitions for performance and
reliability, but this is more work to administer.
> Yes! I know :-((!!! I'm looking for other fs that are journaled like ext3
> or raiserfs but I don't know which are a good choice for stability and
> performances.
The current (0.0.5b) ext3 code is doing pretty good, and if you use
metadata-only journalling it is about as fast as ext2. I still wouldn't
use this on a production system where data loss is fatal, although I
have never had any data loss or filesystem corruption because of ext3.
Cheers, Andreas
--
Andreas Dilger \ "If a man ate a pound of pasta and a pound of antipasto,
\ would they cancel out, leaving him still hungry?"
http://www-mddsp.enel.ucalgary.ca/People/adilger/ -- Dogbert
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2000-11-21 19:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-21 16:58 Ext2 & Performances Roberto Fichera
2000-11-21 18:00 ` Jakob Østergaard
2000-11-21 18:16 ` Roberto Fichera
2000-11-21 18:32 ` Andreas Dilger [this message]
2000-11-21 18:36 ` Aaron Sethman
2000-11-22 5:41 ` Eric W. Biederman
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=200011211832.eALIWDD20416@webber.adilger.net \
--to=adilger@turbolinux.com \
--cc=jakob@unthought.net \
--cc=kernel@tekno-soft.it \
--cc=linux-kernel@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.