4 ms·
If it's not too big, could you just use tmpfs for compilation, and copy the final results to persistent storage if needed? Just food for thought; your point re
by peller 10y ago
If it's not too big, could you just use tmpfs for compilation, and copy the final results to persistent storage if needed?
Just food for thought; your point remains valid.
- toomuchtodo 10y agoDevOps here: This is the solution. Its also stupid fast if everything is done in RAM (just ensure you're not swapping out to disk).
- cgag 10y agoPeople keep saying this but compiling seems super CPU bound so im confused.
- nitrogen 10y agoDisk seeks when lopking up the next file to compile used to be a huge bottleneck.
- hvidgaard 10y agoAt least for C#, it is entirely CPU bound. Faster CPUs and more cores will increase the IO, but not enough to matter anything. But the point about SSD endurance still stands, a ramdisk solves that problem.
- Waterluvian 10y agoWouldn't this possibly be faster too? Is there ever a reason to commit to disk anything you don't keep after a reboot?