Doing a little perspective work in 8.1.48, adding a few named queries etc which requires a project save. My save time is circa 12 seconds, which seems very slow.
In the below screenshot you can see that a save took 12 seconds, the gateway overview shows no recent slow response events. Is the sawtooth profile a bit sharp, suggesting a memory leak, and would that contribute to slow save time? Also shown is ping response time from server to the PC with designer.
All of that looks quite healthy and normal unless someone else can chime in differently. How many resources (views, named queries, etc..) do you have open when you save?
I notice my saves take longer when I have many open. It also depends if there is a lot of retained data saved within bindings and such on the views/windows or a lot going on in each. If I close most of them with no more than a few open, my saves instantly become quicker.
The bigger question is whether your Designer is running out of memory?
How much memory do you have set up for your Designer sessions? Default is only 1GB, and if you have a lot going on on the Designer, maybe its running out as you save?
1 Like
Hey, I’m not at this install right now but I can answer some of these questions. The screenshot shows that, I’m using 441MB/4GB.
I had one view open and 2 NQ’s, so not exactly a lot of resources.
I'd be curious to see if:
- This issue is repeatable after closing / reopening your Designer session on the same machine, especially after a reboot.
- This issue is common to Designer sessions on a different machine.
1 Like
Sorry replied to wrong topic aha.
I will launch a designer session on a laptop here and check the save time.
OK, so I fired up designer on a laptop against the same Gateway.
I opened the project I was working on in my OP, added a comment to a gateway timed script to have some change. No views or NQ’s open. Clicked save, 5 seconds to push.
Then I closed that project and opened a Vision only project. Did the same thing with a GW timer script, clicked save, and took 8 seconds to push.
I will add that this is a Dev Env, uptime is 2 months, so I’m going to do a server reboot here. However, it’s on bare metal Linux, so 2 months uptime should be in no way extreme.
I vaguely recall an issue whereby a few long-running scripts were causing -seemingly- unrelated issues. You showed that there no Slow Response Events, but are there any observable Running Scripts, or an excessive number of Threads, especially Blocked?
1 Blocked thread, trying to recall how to find what that is…
Between pasting that, and returning to the GW webpage, it’s since disappeared…
I saw you were typing a reply, so didn’t reboot yet.
OK, just rebooted, fired up Designer fresh, back to the Perspective project, no views or NQ’s open… did my same Gateway script comment change, save, and 5 seconds.

I did a test on an 8.3.2 Gateway, using the same workstation for Designer as all above (barr the laptop test).

I do plan on moving to 8.3.3 when it’s released on the 20th, but it would still be nice to know the root cause all the same.
In your screenshot, I see the description "...@ 1,000 ms". If so, seems very concerning that your screenshot also captured that script running at 600+ ms for execution time. I'd expect a 1s periodic script to execute sub 10ms every time.
I'm grasping at straws in this recommendation - but consider disabling that script (and others) for a short bit while you attempt to save, see if there's a noticeable difference?
2 Likes
Yes, that just happened to be the execution time, at that time. I watched it for a 10 seconds and it varied 50~600mS. I’ll try optimising that script and or slowing the execution for a while.
1 Like
Are you hopping over VPN’s/the internet from your desinger to the gateway or is it all local?
LAN, 10G Fibre between Designer Workstation and Server.
1 Like
Well it was worth crossing that T. I’d probably contact support at this point if optimizing that long running script didn’t fix it up.