On Wed, Sep 7, 2011 at 02:24, James Broadhead <[email protected]> wrote: > 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. >
Hmmm... that gives me an idea... If I have some free time, I'll experiment with doing an 'emerge -e @world' on the various filesystems, and recording their total time *and* CPU load. Is the `sar` utility good enough to record CPU load? Rgds, -- FdS Pandu E Poluan ~ IT Optimizer ~ • LOPSA Member #15248 • Blog : http://pepoluan.tumblr.com • Linked-In : http://id.linkedin.com/in/pepoluan
