You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We are seeing terrible elevated memory usage in def-use.
We start like this:
PassRepeated invoking DoSimplifyDefUse
ProcessDefUse invoking P4::ComputeWriteSet
heap after P4::ComputeWriteSet: in use 758MB, max 837MB
ProcessDefUse invoking P4::(anonymous namespace)::FindUninitialized
heap after P4::(anonymous namespace)::FindUninitialized: in use 758MB, max 837MB
and end like this:
heap after SimplifyDefUse: in use 9.2GB, max 9.3GB
Note that in the reality the heap mem size query triggers GC collection. In the reality the peak memory usage could be well beyond 16 Gb.
I do not know yet the culprit, still investigating.
The text was updated successfully, but these errors were encountered:
Allocated a total of 2.7GB memory
allocated 737MB in 5576175 calls from:
4 p4c 0x0000000102ff5234 _ZNK2P411Definitions15joinDefinitionsEPKS0_ + 440 0x102ff5234
...
We are seeing terrible elevated memory usage in def-use.
We start like this:
and end like this:
Note that in the reality the heap mem size query triggers GC collection. In the reality the peak memory usage could be well beyond 16 Gb.
I do not know yet the culprit, still investigating.
The text was updated successfully, but these errors were encountered: