Hello!
Screen transitions in vision are too slow. What settings should I change? For reference, I am attaching the modified contents of ignition.conf and screen capacity of the server PC.
screen capacity
ignition.conf : change memory
The server PC's hardware memory is 16GB.
ignition Launcher Setting
It takes more than 10 seconds to switch to the "00_00_HEAT SOURCE FLOW DIAGRAM(IT)" screen. Similarly, switching to the “00_00_HEAT SOURCE FLOW DIAGRAM(UT)” screen also takes more than 10 seconds.
Thanks for your reply.
In vision, the stats of the clients are just as important.
I would start with setting the Client Memory initial setting to the same as the max. This will allocate all the memory at once on the client.
That said, we don't know anything about the content of your windows, or any scripts or queries you have going on.
1 Like
Slow performance, as in "I click something, and _nothing happens for many seconds", in Vision is almost always something slow running on the event dispatch thread. Most often, a user authored script.
By default, all the scripts you write in Vision contexts are running on the primary GUI updating thread - so if a script takes 5 or 10 seconds to run, nothing else in the client GUI can run during that five seconds. I would take a close look at these windows in the Designer and see if you can isolate any possible slow scripts and see if, for instance, disabling these scripts makes your windows open significantly faster.
If that is the case, you'll have to look into patterns to run work asynchronously, such as system.util.invokeAsynchronous. Just pay attention to the fact that any GUI property interactions must happen "back" on the EDT, so you may need to pair with system.util.invokeLater as well.
Fixed that for you. Even property reads can have side effects or yield garbled results. The only thing it is safe to do with a Swing object in a background thread is hold it in a variable in order to hand it back to the foreground.
1 Like
