Details
-
Type:
Story
-
Status: Won't Fix
-
Resolution: Done
-
Fix Version/s: None
-
Component/s: None
-
Labels:None
-
Story Points:10
-
Epic Link:
-
Team:Data Release Production
Description
I have an idea for how to improve Swig build times that we should get vetted (and possibly improved upon) by a true Swig expert (even if that costs a bit of $$). This issue includes vetting that idea (splitting up classes into multiple per-package module builds), getting it through the RFC process, and implementing it in afw.
Attachments
Activity
The sort of things I have in mind should improve both of those - the root problem is that we're just including too much unnecessary code in each of those files.
I think there's at least two issues with how swig is impacting build times. The primary one is obviously the object code build time. I also suspect that may people are also having issues with memory exhaustion on modest hardware (< 16GB of memory) during linking. I haven't closely profiled it but I have seen linking consume in excess of 2GB/process with at least 2 processes running in concurrently.