Hello!
In order to improve the performance of my Ignition Designer, shoud I delete all the unused Named Queries or it doesn´t really matter? Should I also delete unused mockup pages? Unused binding?
I have a lot of those in my current project. Something else?
Cheers!
Do you actually have a performance problem in the designer?
If so, what is the exact nature of your performance problem?
In general, unused resources cost nothing more than disk space and a small amount of memory.
1 Like
Thanks for the answer.
I just get it freeze a lot of times so I do have to close it on my task Manager in order to restart and keep workin. I think I may have to upgrade my PC.
What´s recomended PC requirement to run Ignition Designer?

How much memory do you have allocated to the designer?
What does the CPU usage of the designer process look like in the OS?
The two primary causes of "freezing" in Java Swing applications (which includes Vision and the Designer) are:
- Slow code blocking the event dispatch thread. We have some of that first party still in the designer, but it's pretty few and far between. Vision scripts running inside the designer in preview mode absolutely can affect the rest of the designer, though.
- Memory pressure causing GC stalls, leading to "pause the world" events that manifest as a totally unresponsive application. This will usually manifest as consistently higher CPU usage, as a starved garbage collector constantly tries to stay under the allocated threshold.
1 Like
Ok, thanks will take a look, I already allocated 8,192 mb, I may need to upgrade to 16,384 for memory spikes.
That looks like your memory graph of your gateway, not your designer. The key to the gateway is to look for the classic spikes and drops in the history view of memory usage. To see the memory of your designer, you can look in the bottom right corner of designer or open the Diagnostics window under the Help menu.
1 Like
Oh, thanks, on the designer right bottom corner I got this:

That number will fluctuate (you'll see it in the history graph of diagnostics), but if you're opening/closing projects on a gateway to switch between them without closing the designer, I believe there's a known bug/memory leak that happens, and you just have to close the designer and open a new one to start fresh.
2 Likes
Thanks @michael.flagler , will carefully check out all logs and memory spikes next time it happen so I can do a consistent report on the forum. Cheers!
Also by the graphic, you only have 1 GB allocated for your designer.
Bump that up on the gateway config page.
2 Likes
Ok, thanks, MMaynard, I´m sure it will help

1 Like