Hi,
Is it normal to get ignition designer too heavy and to have tomeouts after working on a project?
I sometimes have problems with this when I switch between buildings and networks. Even then, it is not that common.
There are times where I have a designer open for weeks at a time without issues, don’t judge me 
.
Do you have a query binding that is returning a ton of records or something? Also, on the gateway webpage → gateway settings you can change the max amount of memory the designer can use.
2 Likes
1 Like
I did that at my last job with no problems but where I work now, I’ve ended up with ghost users, especially when the network team makes changes when I’m away...
Yeah, I’ve experienced that when editing a project using a different computer than my workstation. I’m a one-man team, so it doesn’t really affect anything.
1 Like
Actually, I’m building a project. so still making templates of the data-display-blocks so yes i have some query bindings in tens for each block. no tags yet. but noticed that the designer sometimes gets too heavy and unresponsive after hours of work. so, i got worried. as the projects will be much larger and intense in data. i can get better pc for the design stage. but will i face any performance issues when i i commision the project to client? it’s my first time building a project in ignition.
Do check the designer memory allowance first. It is your most likely culprit.
It depends, what are you doing? What’s your connection to the gateway (local, remote, vpn?) Are you working with large datasets, a giant select * query or grouping a lot of things in memory? All of those things can make a designer slow.
I’ve increased it to 4GB. it was on 1GB. and it was almost full almost all of the time.
the heaviness was only while working in the designer. but when opening the session on browser all was good.
Thank you for the advice. i was too engaged in building the interface to the level i forgot about memory.
There's a (set of) longstanding memory leak(s) in the designer that occur when you open additional projects after first launch - this could be what's leading to your issues - someone switching projects often will run into memory issues a lot sooner than someone who always launches into a single project and stays there.
1 Like
Curiosity...
From the design fundamentals of the Designer, from 3rd party libraries IA cannot control, or issues that never made it to the top of the backlog?
Mostly the latter. Unfortunately it's a self perpetuating problem - "hey, this memory leak ticket is on the list, but it's been around a long time and everyone's been dealing with it - let's work on X, Y, or Z that's come in more recently instead, it's higher priority".
1 Like
In a world where most companies ship computers with 16gb of RAM and then you have the nerds (us) boasting much more, it's easy to understand.