From: Hans Reiser <reiser@namesys.com>
To: "Dieter Nützel" <Dieter.Nuetzel@hamburg.de>
Cc: Chris Mason <mason@suse.com>, Oleg Drokin <green@namesys.com>,
ReiserFS List <reiserfs-list@namesys.com>,
JPASTORM@esade.edu
Subject: Re: New to reiserfs
Date: Tue, 14 May 2002 00:57:07 +0400 [thread overview]
Message-ID: <3CE028A3.3080002@namesys.com> (raw)
In-Reply-To: 200205132153.59075.Dieter.Nuetzel@hamburg.de
Dieter Nützel wrote:
>On Monday 13 May 2002 10:07, Hans Reiser wrote:
>
>
>>>>4.- I have a PIII 1 GHz, 512 MB RAM, SCSI server where I run sendmail,
>>>>bind and squid. Will I have problems with performance if I migrate to
>>>>reiserfs?
>>>>
>>>>
>>>>
>>sendmail will be lower in performance when using reiserfs unless you use
>>the latest not yet released patches and turned data journaling on.
>>
>>
>
>More speed numbers on this to come with related post.
>
>
>>Do you really push the performance limits of the machine as a mail server?
>>
>>
>
>You mean if it is worth?
>
>
>
>>squid will benefit from your putting all files in one directory.
>>
>>
>
>So I should clobber my squid partition/dir and reconfigure to put all files
>into only one directory and let the squid hierarchy alone?
>
>Thanks,
> Dieter
>
>
>
I don't understand you.
You should put squid into one big directory (not using their kludge that
avoids making directories too large by using a tree) unless you have
multiple processors (in which case the VFS directory giant lock will
hurt you).
Hans
next prev parent reply other threads:[~2002-05-13 20:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-13 19:53 New to reiserfs Dieter Nützel
2002-05-13 20:02 ` Joe Cooper
2002-05-13 20:57 ` Hans Reiser
2002-05-13 20:57 ` Hans Reiser [this message]
2002-05-13 21:24 ` Dieter Nützel
2002-05-14 13:10 ` Chris Mason
-- strict thread matches above, loose matches on Subject: below --
2002-05-13 9:34 JPASTORM
2002-05-13 9:53 ` Oleg Drokin
2002-05-13 10:07 ` Hans Reiser
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=3CE028A3.3080002@namesys.com \
--to=reiser@namesys.com \
--cc=Dieter.Nuetzel@hamburg.de \
--cc=JPASTORM@esade.edu \
--cc=green@namesys.com \
--cc=mason@suse.com \
--cc=reiserfs-list@namesys.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 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.