On 23 Sep 2017, at 20:03, Cyril Ferlicot D. <cyril.ferlicot@gmail.com> wrote:

Hi,

Can someone explain the real interest to get a dictionary for properties
and a dictionary for queries in the MooseDefaultState?

Is there a downside to merge both?

I did some tests by creating a SYNState using a single dictionary for
both properties and queries. Here is the memory impact:

MooseDefaultState
-------------------

Image without model : 263Mo

Image with model : 605Mo
Image with model and default synectique caches : 650Mo

Image with model, default caches and after using the application : 792Mo

SYNState
-------------------

Image without model : 263Mo
Image with model : 589Mo

Image with model and default synectique caches : 575Mo (There was
probably a full GC that garbaged the temporary object of the import)
Image with model, default caches and after using the application : 706Mo

We see a clear gain of memory. (I did exactly the same interactions in
both try)

We might be interested by this at Synectique. This is why I would like
to know the reasons to have two different dictionaries since there is no
class comment. If the difference will not impact our tools I'll make the
default state configurable and I will introduce this SYNState renaming
it "MooseMemoryEfficientState" if it is fine with everyone.

Thank you in advance for the infos.

--
Cyril Ferlicot
https://ferlicot.fr

http://www.synectique.eu
2 rue Jacques Prévert 01,
59650 Villeneuve d'ascq France

_______________________________________________
Moose-dev mailing list
Moose-dev@list.inf.unibe.ch
https://www.list.inf.unibe.ch/listinfo/moose-dev