All of lore.kernel.org
 help / color / mirror / Atom feed
From: Todd Lyons <todd@mrball.net>
To: ReiserFS <reiserfs-list@namesys.com>
Subject: Re: non volatile ram devices
Date: Thu, 5 Dec 2002 08:21:28 -0800	[thread overview]
Message-ID: <20021205162128.GC4334@mrball.net> (raw)
In-Reply-To: <200212050936.26846.russell@coker.com.au>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Russell Coker wanted us to know:

>It just generally isn't fast enough.  The servers in question have 4 * 72G 
>U160 SCSI disks in RAID-5 arrays on MegaRAID controllers.  They are designed 
>to handle 300,000 accounts for POP and IMAP.
>At times of high load there's 20 reads per second and 160 writes per second.

Let me ask some really stupid questions.
What kind of logging are your pop, imap, and mail services doing?  If
logging to syslog, redirect the mail logging facility to tty12 instead
of a file on the harddrive.  If syslog is logging to a network log
server, then there's not much you can do.  If logging to /dev/null, this
is a non-issue.  Is the Maildir spool on its own partition? (I can't see
how it's not since it's you, Russell).  Is /var/log on its own
partition.

What I'm getting at with all of this is that syslog can create
significant load on a machine if the machine is really busy.

Russell, if you've already tried all this, happily ignore this message
and let us know what you find.
- -- 
Blue skies...		Todd
| Get a bigger hammer!   |  Sometimes you get what you want.      |
| http://www.mrball.net  |  Sometimes you get experience.         |
| http://faq.mrball.net  |                     --unknown origin   |
   Linux kernel 2.4.19-16mdk   1 user,  load average: 0.00, 0.00, 0.00
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)

iD8DBQE9730IIBT1264ScBURAr7lAJ4+19Qrj/aeWSgrOGLHKRvw7jRVqgCg5gZb
+za9M955ADOxSXxlVcOOV6Y=
=e0ai
-----END PGP SIGNATURE-----

  reply	other threads:[~2002-12-05 16:21 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-04 19:59 non volatile ram devices Russell Coker
2002-12-04 20:24 ` Ragnar Kjørstad
2002-12-05  9:00   ` Russell Coker
2002-12-05 10:38     ` Ragnar Kjørstad
2002-12-05 10:45       ` Russell Coker
2002-12-05 13:23     ` Chris Mason
2002-12-06  9:52       ` Russell Coker
2002-12-06 13:03         ` Chris Mason
2002-12-06 23:53           ` Matthias Andree
2002-12-06 23:50         ` Matthias Andree
2002-12-07  4:09           ` Todd Lyons
2002-12-07 17:13             ` Matthias Andree
2002-12-07 10:03           ` Russell Coker
2002-12-07 10:44             ` Valdis.Kletnieks
2002-12-04 22:05 ` Hans Reiser
2002-12-04 21:17   ` Mike Jadon
2002-12-05  6:32 ` Oleg Drokin
2002-12-05  8:36   ` Russell Coker
2002-12-05 16:21     ` Todd Lyons [this message]
2002-12-05 22:51       ` Russell Coker

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=20021205162128.GC4334@mrball.net \
    --to=todd@mrball.net \
    --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.