yade-dev team mailing list archive
-
yade-dev team
-
Mailing list archive
-
Message #00293
Re: Note on optimized compilation / optimized coding / profiling results
Few interesting numbers (from my already optimized version) :
-Each loop on interactions represents 1.47% of cpu time (1.47% = cost of
it++ operator only, disregarding time to access data).
-There are 4 loops in each timestep (Collider, InteractionPhysics,
InteractionGeometry, ContactLaw), so that
InteractionHashMapIterator::increment() represents alone 6% of CPU time.
-InteractionGeometryMetaEngine::action represents 27% of each timestep
(inclusive cost), and elasticContactLaw::action represents 20%. Those
two functions are where most of the mathematics is.
-The time that is really spent for mathematics and associated code is
less than 7% for interaction geometry and less than 12% for ContactLaw
(7 and 12 are estimates based on non-inclusive costs, i.e. time really
spent in contact and geometry dyn libs) .
-Summing : 19% CPU time in maths and 28% in dispatching and operations
on containers.
Bruno
--
_______________
Chareyre Bruno
Maitre de conference
Institut National Polytechnique de Grenoble
Laboratoire 3S (Soils Solids Structures) - bureau E145
BP 53 - 38041, Grenoble cedex 9 - France
Tél : 33 4 56 52 86 21
Fax : 33 4 76 82 70 43
________________
_______________________________________________
yade-dev mailing list
yade-dev@xxxxxxxxxxxxxxxx
https://lists.berlios.de/mailman/listinfo/yade-dev
Follow ups
References