3 ms·
Well, you can always move your code to a ramdisk, I suspect any C(++) isn't more than a few GB anyway ?
by MayeulC 6y ago
Well, you can always move your code to a ramdisk, I suspect any C(++) isn't more than a few GB anyway ?
- biglost 6y agoWith gentoo i use tmpfs and it works really well
- flukus 6y agoMost compilers won't fsync will they? The output is likely not being written straight to disk. It's caches all the way down.
- corty 6y agoBut all compilers will close(). Compare compile times on tmpfs and you will see an improvement.
- rbanffy 6y agoAnd to max out disk bandwidth before you max out your CPU cores you need a really terrible disk. I don't think many 8-way Xeon Platinum boxes have eMMC storage.
- MayeulC 6y agoWell, using ramdisks will let you compare and make sure the disk isn't the bottleneck, at least.
- nwmcsween 6y agoYou don't even need to do this just cat all the files to /dev/null to prime the cache