3 ms·
Chromium is known for taking hours.
by MH15 4y ago
Chromium is known for taking hours.
- redox99 4y agoMore like an hour or less on reasonable, consumer hardware[1]. A lot less on workstation/server CPUs, or with IncrediBuild. [1] https://youtu.be/nRaJXZMOMPU?t=770 https://youtu.be/nRaJXZMOMPU?t=770
- anthk 4y agoMost people will use ccache under Unixen.
- maccard 4y agoAnd for those of us who work primarily with MSVC?
- chlorion 4y agoI am on Gentoo so I have some build time stats! My system has a 3900x, 32GB ram, and a fast NVME SSD for reference. The last chromium build took 1h:45m to complete. This build had LTO enabled and -j18 passed to ninja. Without LTO it would probably be closer to an hour I think but I don't seem to have a non-LTO build in the logs. Your estimation seems pretty accurate!
- nequo 4y agoThat is true. But Chromium is not in the realm in which the compiled vs. interpreted debate is relevant. It is slow to compile, but it would also be very slow to run if it was written in Python. (Unless a hypothetical Node.js rewrite would be comparable on speed. I wonder how it would do on memory.)