Once again, I’d like to point out that if in the Docker image origam-architect doesn’t show any high memory usage, I wouldn’t pay attention to this at all but I still think it wouldn’t hurt to just discuss it anyway, also I am using VISUAL STUDIO in WINDOWS and this can also by the main issue of this topic
I noticed HTML Architect sometimes consumes more than 2 GB, occasionally climbing to 3 GB, BUT the GC does bring it back down to 1–1.5 GB at times. I found that this happens when I open packages in Architect rapidly and continuously.
After opening dotMemory to examine the memory graphs, I noticed that the class FilePersistenceIndex can be the main issue this class is frequently responsible for allocating large numbers of objects PersistedObjectInfo
That’s all for now, I haven’t done a deep analysis yet
Unfortunately the model gets loaded fully to the memory when Architect is opened (at least in the desktop version) in the consistency check process.
Then tree loading is suboptimal as well – in order to load e.g. the data model tree, basically all the xml files get cached under there. If we would improve the model layer so that when asking just for a list of model elements it would not do a deep load, it would improve the performance a lot.
So these are two things:
No need to load everything into memory when doing a consistency check
No need to do a deep load when just getting a list of entities
It would be great to fix. For example, I sometimes use Portainer, and I really enjoy how fast the UI loads and how quickly pages respond. I think that’s great advantage if app loads quickly and doesn’t take a lot of resources
