12 Sep
2010
12 Sep
'10
9:22 p.m.
Good catch. We also had this speedup in VW.
The lazy edges are not related to the node lookup, but to the creation of the edges after
all nodes were created regardless of where in the script they are specified.
Cheers,
Doru
On 12 Sep 2010, at 19:25, Alexandre Bergel wrote:
Hi!
After a short session of pair programming with Henrik, we found places where node lookup
can be severally optimized.
As a result, blueprint complexity opens on 509 classes in 72 seconds.
I know that some issues are still open related to node lookup (lazy edges and
http://code.google.com/p/moose-technology/issues/detail?id=400). I will work on them...
Thanks Henrik!
Cheers,
Alexandre
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
--
www.tudorgirba.com
"Reasonable is what we are accustomed with."