From: Pandu Poluan <pandu@poluan.info>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Filesystem with lowest CPU load, acceptable emerge performance, and stable?
Date: Wed, 7 Sep 2011 19:23:25 +0700 [thread overview]
Message-ID: <CAA2qdGUZKOZsLc_2CqJLUY37e2+Tig9bLj3v33QT=XzRsWEtAg@mail.gmail.com> (raw)
In-Reply-To: <4E675E3C.3000206@binarywings.net>
On Wed, Sep 7, 2011 at 19:06, Florian Philipp <lists@binarywings.net> wrote:
> Am 06.09.2011 21:24, schrieb James Broadhead:
>> On 6 September 2011 19:55, Permjacov Evgeniy <permeakra@gmail.com> wrote:
>>> On 09/06/2011 09:26 PM, Pandu Poluan wrote:
>>>> Disk I/O Characteristic: Occasional writes during 'normal' usage,
>>>> once-a-week eix-sync + emerge -avuD
>>>> Priority: Stable (i.e., less chance of corruption), least CPU usage.
>>
>> You would have to profile this, but I imagine that the best approach
>> would be to compile in a RAM disk and copy. I think that you're
>> probably trying to optimise the wrong part of this problem.
>>
>> As for ext3/ext4, the improvements to fsck alone make ext4 the FS of
>> choice between the two.
>>
>> JB
>>
>
> Pandu is building a firewall. Putting a ton of RAM in it just for the
> sake for system updates is plain overkill and -- depending on his IaaS
> provider -- pretty expensive.
>
Indeed. If I need more RAM, they will only sell a complete package of
vCPU+RAM+Storage, which will then be merged with my current package.
They do offer Storage-only add-on packages, though. But that's beside the point.
Rgds,
--
FdS Pandu E Poluan
~ IT Optimizer ~
• LOPSA Member #15248
• Blog : http://pepoluan.tumblr.com
• Linked-In : http://id.linkedin.com/in/pepoluan
next prev parent reply other threads:[~2011-09-07 12:24 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-06 17:26 [gentoo-user] Filesystem with lowest CPU load, acceptable emerge performance, and stable? Pandu Poluan
2011-09-06 17:52 ` [gentoo-user] " Pandu Poluan
2011-09-06 18:07 ` Florian Philipp
2011-09-06 18:15 ` [gentoo-user] " kashani
2011-09-07 12:25 ` Pandu Poluan
2011-09-07 22:15 ` kashani
2011-09-08 7:52 ` Pandu Poluan
2011-09-08 22:26 ` kashani
2011-09-06 18:55 ` Permjacov Evgeniy
2011-09-06 19:18 ` Michael Mol
2011-09-06 19:24 ` James Broadhead
2011-09-07 12:06 ` Florian Philipp
2011-09-07 12:23 ` Pandu Poluan [this message]
2011-09-07 12:28 ` Pandu Poluan
2011-09-07 21:24 ` Jesús J. Guerrero Botella
2011-09-09 7:36 ` Andrea Conti
2011-09-10 5:43 ` Walter Dnes
2011-09-11 21:02 ` Jesús J. Guerrero Botella
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='CAA2qdGUZKOZsLc_2CqJLUY37e2+Tig9bLj3v33QT=XzRsWEtAg@mail.gmail.com' \
--to=pandu@poluan.info \
--cc=gentoo-user@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