Thread overview
[Issue 18843] -deps -unittest causes cataclysmic memory usage
May 08, 2018
Seb
Dec 17, 2022
Iain Buclaw
May 08, 2018
https://issues.dlang.org/show_bug.cgi?id=18843

Seb <greensunny12@gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |greensunny12@gmail.com

--- Comment #1 from Seb <greensunny12@gmail.com> ---
Please see and help out on https://github.com/dlang/dmd/pull/8124

--
December 17, 2022
https://issues.dlang.org/show_bug.cgi?id=18843

Iain Buclaw <ibuclaw@gdcproject.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Priority|P1                          |P3

--
March 27
https://issues.dlang.org/show_bug.cgi?id=18843

--- Comment #2 from FeepingCreature <default_357-line@yahoo.de> ---
Note: This has gotten a lot better at some point, great job! But running with `-deps` still brings the time for a simple Hello World up from 250ms wallclock to 440ms wallclock. It is thus still unusable, as its whole point would be speeding up compiles, and as it stands I can get the import graph of projects a lot faster by just grepping for `import`.

--
March 27
https://issues.dlang.org/show_bug.cgi?id=18843

--- Comment #3 from FeepingCreature <default_357-line@yahoo.de> ---
Actually, I just tried this on a bit bigger project. And if there's a lot of imports, it looks more like 1s (no -deps=) vs 5s (with -deps=). Looks like it's mostly Semantic3OnDependencies, which makes sense if `-deps` forces compilation so it can look inside for more imports. So I'd still need a way to limit the scope of `-deps` from the commandline.

--