Every single call of this function results in memory allocation. I have narrowed it down to the call to Jacobiansurface: if that call is eliminated, there is no memory allocation. function Jacobianvolume{T<:FESet2Manifold}(self::FEMMBase{T}, J::FFltMat, loc::FFltMat, conn::FIntMat, N:…

Dispatch doesn’t propagate type info for keywords, so FESetT3 is typed as Any. Here is the problematic code: type FESetT3 <: FESet2Manifold nfensperfe::FInt conn::FIntMat label::FIntVec function FESetT3(; conn::FIntMat=[], label =zero(FInt)) const nfensperfe::FInt = 3 @assert (s…

Weird memory allocation

General Usage

PetrKryslUCSD May 18, 2017, 11:53pm 3

If Jacobiansurface() does not get called, no allocation; if it does, there is an allocation.

Topic		Replies	Views
Inappropriate memory allocation? Julia at Scale question , memory	24	2226	September 4, 2017
Finding the memory allocation in some code General Usage performance	3	879	August 25, 2017
Memory allocations in for loop variable Performance question	28	3722	August 31, 2018
Memory allocations are not very understandable Performance	26	2025	December 12, 2017
Reducing allocations to optimize (to match Java speed) Performance	22	1405	December 10, 2018

Weird memory allocation

Related topics