On Wed, 2012-06-13 at 09:22 +0200, Josselin Mouette wrote: > Le mercredi 13 juin 2012 à 04:14 +0300, Serge a écrit : > > Yes. Everything. Every popular /tmp usage that most users expect to work > > is limited either by CPU (gcc compiling) or by network speed (browser or > > flash temporaries), or is just too fast already (bash heredoc). So moving > > /tmp to tmpfs does not make them faster, but can break them instead (if > > there's not enough space to store a streamed video, for example). > > You should really back up claims such as “GCC is CPU-bound” with data. > > Because it sounds to me that when building with make -j8 on a fast > multi-core system, you will hit the IOPS limit of a rotating drive very > quickly. [...]
It's fine with a local disk and enough RAM for a decent disk cache. (NFS is another matter.) Ben. -- Ben Hutchings Computers are not intelligent. They only think they are.
signature.asc
Description: This is a digitally signed message part
