5 ms·
What about spinning up a 24core vm and mount your code with sshfs for those compiles? Edit: corrected ashes to sshfs
by spockz 6y ago
What about spinning up a 24core vm and mount your code with sshfs for those compiles?
Edit: corrected ashes to sshfs
- leetcrew 6y agothis has been discussed internally. for a variety of reasons, testing the software on a remote machine is kinda painful, so we would still have the overhead of copying the executable back to the developer's machine. the more straightforward approach is just to buy fast desktops for all the devs. a desktop with 32GB ram, a top of the line consumer cpu, and a middling gpu is roughly the same price as a good ultrabook anyway. also, c++ compilation doesn't scale perfectly with more cores. linking is still single threaded, AFAIK.
- PaulDavisThe1st 6y agolld will parallelize your link step. Major improvement over ld. Barely any change to the rest of your build process.
- pdimitar 6y agoHave you tried it with a Rust project? Is there a real gain? Really curious and willing to try.
- StillBored 6y agosshfs adds far to much latency to large compiles which tend to open a ton of little files, read a KB or two, and close them. If your on a local LAN its doable on NFS or other low latency network sharing, but for everything going over the internet ssh is going to be far to slow. In those cases its better to just git pull the changes and maintain a local copy on the compile target.
- sukilot 6y agoWhat do you mean? The code is on the build server. You only need to push your human-timescale changes.