Hey hey, Even though I know performance wasn't part of this sprint's focus, I felt the long indexing times were slowing down development and testing more than necessary, so I've spent some time improving dxr-index.py and the clang plugin to have it perform better.
With these patches [1], more operations happen directly on the database instead of building the data map on memory, the result is that memory usage has been decreased to 25% of the original one and the overall indexing + html generation time has gone down from ~3h30m to 40-45m [2] Of that reduced time, the first 1/3 is spent on creating the database, the other 2/3 are spent on generating the html pages (~56K), which results on an avg of 35-37 pages per second being created, I think this timing is good enough to consider dynamic generation of source code pages :). dxr.lanedo.com now uses those patches for indexing, there shouldn't be any major visible difference, so please tell me if there's some inconsistency I oversaw. Cheers, Carlos [1] https://github.com/garnacho/dxr/compare/2f6a5d348a...da902df303 [2] using mozilla-central _______________________________________________ dev-static-analysis mailing list [email protected] https://lists.mozilla.org/listinfo/dev-static-analysis
