Hi all, I was just wondering if anyone else has been noticing that 8.3 has caused significant load issues even in the Designer.
Comparing to other projects I've built in Perspective, I don't remember designing mimics taking this long. The other pages I've done have had pipes and mostly the same embedded views on them to make up valves, pumps, etc., but on 8.3 it's so hard to make anything (or line anything up) due to the significant lag.
Creating pipes is a nightmare because it now takes a solid 3 seconds for my pipes to start moving when I drag to make new paths. Moving objects also visually lags around the page. When I try to highlight anything I miss half the stuff because the selected area is 100px off from where I started, haha.
In my Designer I've assigned 4GB of memory but it hang around close to 1GB. I'm starting to go through and change my views to blocking to see if this helps. The only reason I haven't gone back to 8.1 (I think that was the one I used) is the object drawing and I hear that some new changes to the historian's load times.
I'm just worried that when it comes to installing on site it'll be very slow. Did anyone have any tips, or is anyone facing similar issues?
Thanks
I haven't noticed any of these lagging issues myself. When you're creating pipes, do you have a separate coord container to hold your pipes, or are you trying to add pipes into the same coord container as all your other embedded views/components? If you're doing the latter then this is most likely the reason, since there will be snap points created for every single component, and if you have a lot of these on the screen, these are all added into the DOM on the page which slows things down.
I do have a lot of them in the same view so that explains the pipes. On my next page ill try and put these into coordinate containers or ill see if I can move them to their own container. Thank you.
I assume this also effects all the embed view's, trying to move anything would cause them to hit all the anchors.
The only other issues that i cant explain is the lag it takes to shift objects upwards via the arrows keys as well as trying to drag and select anything. I'm also concerned by the load times of the pages but this could just be issues relating to my Dev PC.
So i got one of my more congested pages, moved the pipes to their own coordinate container and filmed the following. The pipes are snapping to other pipes
what are the specs of the PC running your gateway and the designer?
I am running it in a VM and have assigned it 8 GB of ram and 8 Processor cores
Are you running the Designer (allocated 4GB) within the same VM? Assuming Windows VM too
yes altho i tried dropping it to 2 GB as i was never reaching the upper limit
What if you try running the Designer outside of the VM?
I have a co-worker who is running into the same issues and they are running it on their base machine. 32 GB of ram, 22 processor cores and having the same issues.
In the next day or so i will be transferring it to a more powerful computer so i will see how it goes but i just don't believe i have run into this kind of lag before.
Sorry about the delay, I was finally able to move it onto a new PC with purely ignition installed on it to test and it was still very laggy to design anything. It was slightly better than before but still very sow to use.
The PC has 64 GB of ram, M.2 SSD, i9 24 core so the PC has some powerful specs. I feel like perspective can't handle the amount of pipes and objects I have on the page.
I tried it with the pipes in their own container and on the root container and there was no difference.
Id like to also mentioned that its not just the pipes, its all objects, containers, embed views labels, ect
I wonder if Windows is assigning efficiency cores of your i9 to the process rather than performance cores. I've had that issue with VMs in the past causing them to be very laggy.
I will look into that for the dev computer as I will be going back to VM's for other projects. Thank you
The video above is on the new PC and ignition was installed directly to it, no VM's.
Hi,
I am having the same problems. Running from my base, not a VM.
Any pointers?
The video above looks like a lot of resources being sucked up on the view. I'd be looking at the view itself. For your question, we'd need some more info to be helpful: What projects/components? Have you tried a fresh project, and have issues? Can you take just one piece at a time and see what's causing the slowdown? That kind of thing.
The issue of Windows assigning efficiency cores isn't limited to VMs. It can do it to any app running on your computer including Ignition.
I'd start with a fresh gateway/project with a blank view and add just 2-3 components and see how it performs. Don't add any extra 3rd party modules or anything. No scripting, nothing. Just a blank project/gateway.
How many pipes are we talking? How many other components?
I haven't tried it before, but I wonder if the dev tools' performance diagnostics might help? You can open the dev tools inside the designer, from memory it's called external debugger in the help or tools menu
Gemini reckons it would be useful
"Browser DevTools (specifically the Performance and Network tabs) isolate whether an Ignition Perspective view is suffering from client-side DOM overhead, JavaScript execution bottlenecks, or Gateway-to-client WebSocket/HTTP transport latency."
This might be useful to run to give you the total number of nodes on the page
console.log(document.querySelectorAll('*').length)
You would run this inside the dev tools console
AI step by step (not tested, and I don't have experience to know if this is useful at all)
Thank for the tip with the diagnostics, i was able to views my embedded views and optimise them to improve performance. Turns out i had 15137 nodes and i was able to get it down to 13000. still alot but i cant see anyway to reduce it.
Un fortunately as its a mimic i have a lot of embed views, close to 180. I guess there just isn't much that i can really do. I could have sworn on other projects i have had large pages like this with more embedded views. I have removed animations and taken the labels out of embedded views an just replaced them with generic labels. It is built upon another project so ill see how i go with just importing the elements on just that page and testing it out.
If you want to send me a copy of the project, I can try having a clanker (ai agent) "flatten" out the page so the components are placed directly instead of using embedded views. I've found that there can be a performance hit by using embeds in the past. Not sure it will help, but maybe worth a shot.
