3 ms·
Compilation doesn't sound like an I/O intense workload. It's more CPU intense. Some heavy DB usage or video editing on the other hand is I/O intense.
by shmerl 9y ago
Compilation doesn't sound like an I/O intense workload. It's more CPU intense. Some heavy DB usage or video editing on the other hand is I/O intense.
- rleigh 9y agoCompilation itself, no. However, linking can be very I/O-intensive, particularly if using static linking of large libraries. And packaging up of build products at the end of the process. These can often be serial rate-limiting steps in comparison with parallelised compilation, so can end up taking a disproportionate fraction of the total wall clock time. While it can clearly vary widely depending upon the nature of what you are building, it can in some cases be worth using faster storage to shave many tens of minutes off the build time.