On Wed, Sep 7, 2011 at 19:06, Florian Philipp <[email protected]> wrote: > Am 06.09.2011 21:24, schrieb James Broadhead: >> On 6 September 2011 19:55, Permjacov Evgeniy <[email protected]> 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
