Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Weird memory allocation report #34054

Closed
PetrKryslUCSD opened this issue Dec 9, 2019 · 0 comments
Closed

Weird memory allocation report #34054

PetrKryslUCSD opened this issue Dec 9, 2019 · 0 comments

Comments

@PetrKryslUCSD
Copy link

With Julia 1.3, julia --track-allocation=user. The measurement was collected during a second run, after clearing the malloc data after the first run. Code fragment from a .mem file:

        0     lambda = E * nu / (1 + nu) / (1 - 2*(nu));
        0     mu = E / 2. / (1+nu);
   860578     mI = diagm(0=>[1, 1, 1, 0.5, 0.5, 0.5]);
      768     m1m1 = _m1*_m1';
  3499241     I3 = [1.0 0 0; 0 1.0 0; 0 0 1.0]
     2016     b = [0.0 0 0; 0 0.0 0; 0 0 0.0]
     2016     sigma = [0.0 0 0; 0 0.0 0; 0 0 0.0]
     6560     return MatDeforNeohookean(mr, mass_density, E, nu, lambda, mu,
        - 		              tangentmoduli3d!, update3d!, 
        - 		              deepcopy(mI), deepcopy(m1m1), deepcopy(I3), deepcopy(b), deepcopy(sigma))

How does one interpret the above? The function with this code is called once.
Where does all the allocation come from?

vtjnash added a commit that referenced this issue Jan 3, 2020
Don't include one-time costs (JIT compilation) so that warm-up isn't generally required.
And adjust codegen emission to charge call entry costs to the caller.

fixes #11753
fixes #19981
fixes #21871
fixes #34054
close #18595
vtjnash added a commit that referenced this issue Jan 15, 2020
Don't include one-time costs (JIT compilation) so that warm-up isn't generally required.
And adjust codegen emission to charge call entry costs to the caller.

fixes #11753
fixes #19981
fixes #21871
fixes #34054
close #18595
vtjnash added a commit that referenced this issue Jan 21, 2020
Don't include one-time costs (JIT compilation) so that warm-up isn't generally required.
And adjust codegen emission to charge call entry costs to the caller.

fixes #11753
fixes #19981
fixes #21871
fixes #34054
close #18595
KristofferC pushed a commit that referenced this issue Apr 11, 2020
Don't include one-time costs (JIT compilation) so that warm-up isn't generally required.
And adjust codegen emission to charge call entry costs to the caller.

fixes #11753
fixes #19981
fixes #21871
fixes #34054
close #18595
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant