From: Mike Looijmans <mike.looijmans@topic.nl>
To: <yocto@yoctoproject.org>
Subject: Re: tmp on NFS
Date: Wed, 7 Oct 2015 15:39:17 +0200 [thread overview]
Message-ID: <56152085.30203@topic.nl> (raw)
In-Reply-To: <CAJTo0LYq2JgWo953QYT2nQrdqVtG5yObUuMvmYLYJ0YWzbMsKA@mail.gmail.com>
On 07-10-15 15:04, Burton, Ross wrote:
>
> On 7 October 2015 at 13:59, Burton, Ross <ross.burton@intel.com
> <mailto:ross.burton@intel.com>> wrote:
>
> Follow the link in the patch to the referenced bug, and comment #8 by Mark
> Hatle explains the problems that Wind River were seeing in testing:
>
>
> I should also add that many people buy lots of RAM and do builds with
> build/tmp in a tmpfs as it gives you a noticeable performance increase, so I
> dread to think how much it will hurt to do a build with build/tmp on a network
> mount.
Telling Ubuntu to actually use all that RAM for some serious caching (e.g.
allow 50% dirty pages, and extend the timeout to several minutes), and (if you
have >14) putting cfq back into its rightful place as io scheduler made a huge
difference for me.
Kind regards,
Mike Looijmans
System Expert
TOPIC Embedded Products
Eindhovenseweg 32-C, NL-5683 KH Best
Postbus 440, NL-5680 AK Best
Telefoon: +31 (0) 499 33 69 79
Telefax: +31 (0) 499 33 69 70
E-mail: mike.looijmans@topicproducts.com
Website: www.topicproducts.com
Please consider the environment before printing this e-mail
prev parent reply other threads:[~2015-10-07 13:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-07 1:37 tmp on NFS Luke (Lucas) Starrett
2015-10-07 7:01 ` Mike Looijmans
2015-10-07 12:59 ` Luke (Lucas) Starrett
2015-10-07 12:59 ` Burton, Ross
2015-10-07 13:04 ` Burton, Ross
2015-10-07 13:39 ` Mike Looijmans [this message]
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=56152085.30203@topic.nl \
--to=mike.looijmans@topic.nl \
--cc=yocto@yoctoproject.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 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.