I've had been doing this on my laptop with only an SSD in hopes of
saving write cycles, but eventually I gave up. Far too many situations
where the battery died and I had to do a full rebuild.
I was thinking of writing some caching script that would save
not-so-often changed objects to the SSD an
I have a plain old mechanical disk too, but I have 32 G of RAM, enough that
disk access is not relevant to my (unified) build times. After a build, I
have 12 to 14 G of RAM used for cache, so I suppose that disk performance
is still relevant if you have <= 16 G of RAM, yeah.
Benoit
2014-07-19 1:
Ah yes, I forgot to say. I am on Linux. I've found using RAM instead of
my (mechanical) disk saves about 5 minutes of a roughly half-hour build.
GL
On 19/07/14 16:24, Benoit Jacob wrote:
What OS are we talking about?
(On Linux, ramdisks are mountpoints like any other so that would be
trivial;
What OS are we talking about?
(On Linux, ramdisks are mountpoints like any other so that would be
trivial; but then again, on Linux, the kernel is good enough at using extra
RAM for disk cache automatically, that you get the benefits of a RAMdisk
automatically).
Benoit
2014-07-18 22:39 GMT-04:0
Today I tried to build Firefox on a RAM disk for the first time, and
although I succeeded through trial and error, it occurs to me that there
are probably things I could do better. Could someone who regularly does
this make a blog post or an MDN page about their workflow and some tips
and trick
5 matches
Mail list logo
