From: "H. Peter Anvin" <hpa@zytor.com>
To: Hugh Dickins <hugh@veritas.com>
Cc: Tomasz Chmielewski <mangoo@wpkg.org>,
LKML <linux-kernel@vger.kernel.org>,
Mika Lawando <rzryyvzy@trashmail.net>
Subject: Re: What is the limit size of tmpfs /dev/shm ?
Date: Wed, 06 Feb 2008 11:53:19 -0800 [thread overview]
Message-ID: <47AA102F.1070105@zytor.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0802061938120.32204@blonde.site>
Hugh Dickins wrote:
>
> In theory, yes, and should be true in practice before it hits swap.
> But I think you'll find our swap handling is too primitive for tmpfs
> to perform well once we hit swap. Most filesystems pay considerable
> attention to good performance within their constraints of correctness.
> Whereas with tmpfs we've just never worried about the performance once
> swapping. It's used so you don't lose your data, but if you're really
> expecting to be going to disk very much, better start with a filesystem
> really designed for that.
>
That sounds like a problem in our overall swap handling, not
specifically in tmpfs. Now, I can't say anything concrete about heavy
swap conditions, but in light swap conditions I have measured a 20x
performance improvement(!) over ext3 on real workloads.
-hpa
next prev parent reply other threads:[~2008-02-06 19:53 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-06 14:54 What is the limit size of tmpfs /dev/shm ? Tomasz Chmielewski
2008-02-06 15:06 ` rzryyvzy
2008-02-06 15:29 ` Hugh Dickins
2008-02-06 19:27 ` H. Peter Anvin
2008-02-06 19:48 ` Hugh Dickins
2008-02-06 19:53 ` H. Peter Anvin [this message]
2008-02-06 21:58 ` Hugh Dickins
2008-02-06 22:01 ` H. Peter Anvin
2008-02-06 22:40 ` Hugh Dickins
-- strict thread matches above, loose matches on Subject: below --
2008-02-06 13:54 Mika Lawando
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=47AA102F.1070105@zytor.com \
--to=hpa@zytor.com \
--cc=hugh@veritas.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mangoo@wpkg.org \
--cc=rzryyvzy@trashmail.net \
/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.