From: Rich Freeman <rich0@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] rfc: use of the /run directory
Date: Tue, 17 May 2011 16:23:50 -0400 [thread overview]
Message-ID: <BANLkTimSGwcmRJdViC4AWZNy11VWWxYSew@mail.gmail.com> (raw)
In-Reply-To: <1305662441.2645.1.camel@TesterTop4>
2011/5/17 Olivier Crête <tester@gentoo.org>:
> On Wed, 2011-05-18 at 01:18 +0530, Nirbheek Chauhan wrote:
>> Maybe you should use /var/tmp for that? Or ~/tmp/ ?
>>
>> OTOH, we could use an rc.conf configuration variable to control
>> whether /tmp is mounted as tmpfs.
>
> Having /tmp and /var/tmp as tmpfs sounds like a terrible idea.. I don't
> think we should facilitate it in any way.
I've run my system this way for ages - even back when I had 2GB of RAM
running kde, samba, mythtv, mysql, and apache. Usually not a problem.
Unfortunately the kernel swapping logic isn't perfect, which can
cause it to bog down if you're compiling something like chromium or
openoffice.
When you think about it tmpfs on swap should be no slower than ext3.
If anything it should be faster since it doesn't need to journal. In
practice it doesn't always work this way, but I'd consider this a bug.
With a filesystem, anything you write ends up on disk within 30
seconds or whatever. With a tmpfs, some of the stuff you write ends
up on disk, and the kernel has more freedom with how it goes about
doing this.
Then problem comes when the kernel decides to swap out mysql or
whatever in order to hang onto some pages full of .so files or
whatever from your latest build.
Rich
next prev parent reply other threads:[~2011-05-17 20:25 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-17 16:57 [gentoo-dev] rfc: use of the /run directory William Hubbs
2011-05-17 18:11 ` Peter Volkov
2011-05-17 18:28 ` Nirbheek Chauhan
2011-05-17 18:43 ` Ângelo Arrifano
2011-05-17 18:50 ` Nirbheek Chauhan
2011-05-17 19:11 ` Peter Volkov
2011-05-17 19:20 ` Ângelo Arrifano
2011-05-17 19:07 ` William Hubbs
2011-05-17 20:35 ` James Cloos
2011-05-17 20:40 ` Markos Chandras
2011-05-18 0:06 ` James Cloos
2011-05-18 0:43 ` William Hubbs
2011-05-17 19:20 ` Panagiotis Christopoulos
2011-05-17 19:46 ` William Hubbs
2011-05-18 1:31 ` [gentoo-dev] " Duncan
2011-05-18 1:36 ` [gentoo-dev] " Jeroen Roovers
2011-05-18 5:49 ` Eray Aslan
2011-05-18 14:45 ` Henry Gebhardt
2011-05-18 14:51 ` Samuli Suominen
2011-05-18 15:02 ` [gentoo-dev] " Jonathan Callen
2011-05-17 19:48 ` [gentoo-dev] " Nirbheek Chauhan
2011-05-17 20:00 ` Olivier Crête
2011-05-17 20:07 ` Michał Górny
2011-05-17 20:11 ` Amadeusz Żołnowski
2011-05-17 20:23 ` Rich Freeman [this message]
2011-05-17 20:20 ` Panagiotis Christopoulos
2011-05-17 20:28 ` Michał Górny
2011-05-17 20:54 ` Olivier Crête
2011-05-17 21:00 ` Nirbheek Chauhan
2011-05-17 22:26 ` Drake Wyrm
2011-05-17 22:36 ` Marc Schiffbauer
2011-05-17 22:46 ` Nirbheek Chauhan
2011-05-18 0:06 ` William Hubbs
2011-05-17 22:50 ` Ciaran McCreesh
2011-05-18 0:12 ` William Hubbs
2011-05-23 6:30 ` Ciaran McCreesh
2011-05-23 7:05 ` Nirbheek Chauhan
2011-05-23 7:11 ` Ciaran McCreesh
2011-05-23 7:13 ` Michał Górny
2011-05-23 8:30 ` Nirbheek Chauhan
2011-05-20 8:58 ` Luca Barbato
2011-05-20 16:54 ` Mike Pagano
2011-05-22 19:13 ` Luca Barbato
2011-05-22 21:12 ` Ondřej Súkup
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=BANLkTimSGwcmRJdViC4AWZNy11VWWxYSew@mail.gmail.com \
--to=rich0@gentoo.org \
--cc=gentoo-dev@lists.gentoo.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox