On Wed, 7 Jan 2015 15:22:46 -0500, Rich Freeman wrote: > > That's not what I meant, but I see your point about using --reflink if > > making copies. My thought was to forget the whole tmpfs and copying > > think, set KEEP WORK in FEATURES and use XFS for PORTAGE_TMPDIR. That > > way most of the work is taking place in the cache without the > > frequent disk writes of other filesystems. I would expect XFS to be > > faster for this job, but have no data to support that assumption. > > > > Or you could just put TMPDIR on btrfs and snapshot after each emerge. > > > > If you're not going to move it but just leave it all in > TMPDIR forever, then by all means use whatever filesystem you like.
Of course, but the original question was about improving performance (via tmpfs) and a heavily cached filesystem should go partway towards that. Mind you, ext2 would also help as it would avoid the journal overhead. > Sure, > you could snapshot it and clean it, but that might not be the > cleanest way. You'd have to manager the snapshots, but then you'd have to manage any form of copies if you don't want to run out of disk space, but at least it would be fast. -- Neil Bothwick Welcome to the world of Windows 95. Stay a while -- stay foooreveeer.
pgp1TXxDGI769.pgp
Description: OpenPGP digital signature
