5 ms·
I don't know if SCons is still slow, but in 2018 it was definitely very, very slow. I doubt it has improved much, as its maintainers were in similar denial then
by ncmncm 6y ago
I don't know if SCons is still slow, but in 2018 it was definitely very, very slow. I doubt it has improved much, as its maintainers were in similar denial then.
When we used it at MongoDB, somebody (thanks Mathias!) put together apparatus to make it generate a ninja config instead of building by itself. That was fast! Anyway, after you had the ninja config.
But the edit-build-test cycle did not include a slow SCons run anymore, and that was huge.
The MongoDB internal wiki had a page titled "SCons Isn't That Slow", with advice for how to live with how slow it really was, later including ("unofficial") ninja and ccache setup. (Which I added.)
But at least it wasn't WAF.
- bb88 6y agoIf forking is the issue, why didn't they just do multiprocessing instead with a bunch of worker processes and work going into queues?
- jhasse 6y agoWhy is Waf slower? It has separate config / build steps.
- ncmncm 6y agoI don't recall (from time-served at Bloomberg) that Waf was especially slow, but I found that to make it do anything useful, you had to write a lot of obscure, custom Python code nobody could understand.
- jhasse 6y agoAnd you think this custom Python code wouldn't have been necessary with SCons?
- ncmncm 6y agoDon't really know, tbh. Things I used SCons on were different from the things I used Waf on. SCons might need as much custom Python for those other uses as Waf. But that does not make Waf any better.
- jhasse 6y agoI'm still wondering what makes Waf worse in your opinion, if it wasn't performance or custom code required.
- ncmncm 6y agoUnpleasant memories, which might be mixed up in the Bloomberg experience. To ne the overriding criterion for a build system is that it must not demand attention. Waf did. SCons seemed not to.
- bsder 6y ago> I don't know if SCons is still slow, but in 2018 it was definitely very, very slow. I doubt it has improved much, as its maintainers were in similar denial then. And, at this point, its time has passed. The big projects that were using scons all moved on to other systems for various reasons. Better to move on to something that actually might generate a critical mass and community.
- onebaddog 6y agoActually not true. Many large projects continue to use SCons and new projects as well. I don't think in 2018 we had our heads in the sand about SCons' performance. As project maintainer I've (along with other community members) have been working on performance since at least 2016.
- ncmncm 6y agoIf you had a hand in getting it to generate ninja scripts: Congratulations. That made a big improvement in the daily experience of people maintaining projects built under SCons. To be clear: SCons is not notably worse at describing what must be done to build a big project than other systems of its time. Lots of code has been compiled under it. Its deep failure has been in trying to direct the activities of compilations in real time, at which it is bad, gmake is good, and ninja positively excels. Still, slowness in resolving dependencies is hard to defend. It is a problem in operations long well-understood, with familiar algorithms. A data structure well tuned to the algorithm would make even Python able to solve it quickly enough. Nowadays the difficult part of a build system is the complexities of managing foreign dependencies, at which CMake is only just adequate.