Ticket #10700 (assigned)

Opened 6 years ago

Last modified 5 years ago

Huge memory usage compiling Kernel with clang.

Reported by: Martyn Gigg Owned by: Peter Peterson
Priority: major Milestone: Release 3.5
Component: Framework Keywords:
Cc: Blocked By:
Blocking: Tester:

Description

I was having a quick play with the include-what-you-use tool after merging in the changes from #10685 locally. It seems that clang requires about ~12Gb of memory to compile Kernel. It looks as if it is the linking step that ramps up the memory usage.

I don't it's anything to do with those changes but something about the code in Kernel. We should find out why.

It's worth noting that when compiling with gcc the linking step seems to take a disproportionate amount of time to the size of the library.

My suspicion is all of the static objects in Atom.cpp but that's just a guess.

Change History

comment:1 Changed 6 years ago by Martyn Gigg

  • Status changed from new to assigned

comment:2 Changed 6 years ago by Martyn Gigg

Pete, I assigned this to you just because you had #10685 and I wanted to make sure we didn't forget about it.

comment:3 Changed 5 years ago by Nick Draper

  • Milestone changed from Release 3.4 to Release 3.5

Moved to R3.5 at the R3.4 code freeze

comment:4 Changed 5 years ago by Stuart Campbell

This ticket has been transferred to github issue ​11542

Note: See TracTickets for help on using tickets.