Gibbs lag / delay v14 and v13

[guidoc]

I think this has been discussed before, but I don't think it has been brought up in the context of v14 (maybe buried in a thread somewhere?)

When I double click a process to load the dialog box there is considerable lag before the process dialog box pops up. Best is 2-3 seconds, it is usually 5-10 seconds. There is also a lag when closing the process box (X in the upper right of the process box) of 2-3 seconds. Tool dialog boxes are quick, just the process dialog.

I did see this on 13.0.33 and 13.0.26. I upgraded to 14.0.8 hoping this would go away, but sadly it hasn't.

This is a decently beefy computer - quadro P4000 on an i7 8700k w/32gb ram and ssds. I do have dual 4k monitors, but I seriously doubt that a dialog box popup is really taxing the graphics card to the point of lag, especially if other boxes are quick.

Is anyone else experiencing this?

[JeremyS]

I think this has been discussed before, but I don't think it has been brought up in the context of v14 (maybe buried in a thread somewhere?)

When I double click a process to load the dialog box there is considerable lag before the process dialog box pops up. Best is 2-3 seconds, it is usually 5-10 seconds. There is also a lag when closing the process box (X in the upper right of the process box) of 2-3 seconds. Tool dialog boxes are quick, just the process dialog.

I did see this on 13.0.33 and 13.0.26. I upgraded to 14.0.8 hoping this would go away, but sadly it hasn't.

This is a decently beefy computer - quadro P4000 on an i7 8700k w/32gb ram and ssds. I do have dual 4k monitors, but I seriously doubt that a dialog box popup is really taxing the graphics card to the point of lag, especially if other boxes are quick.

Is anyone else experiencing this?

In 14 it is likely more prevalent than in 13. The process dialogs have slowly (over the last several releases) been moved to a new framework, 14 finished that migration. We are aware of the slowness in opening the dialogs and are investigating the source of the issue. In 13, what process dialogs did you see this happening in?

[guidoc]

Thanks Jeremy. All of them are slow. I think volumill was the slowest, but they all are very slow to load.

[GDNT]

I have experienced exactly the same issue with 14.0.4.0 as Guidoc described above, but my lags were in the 1 to 2 second range.

[Phil Holtzleiter]

I have experienced exactly the same issue with 14.0.4.0 as Guidoc described above, but my lags were in the 1 to 2 second range.

Same here, but on 14.0.08. I've gone back to 13 for now until this gets resolved.

[Metco]

it slows down dramatically if i open another instance of GC otherwise its only about 2 sec slower than V13..
but if you open 2 or 3 instances on different monitors ya there is a alot of LAG opening dialogs..

[ComputekEng]

yea this is why im not using v14. seems like a lot if QOL but the lag and slow dialogs negate any advantage. even a simple drilling op window takes 5 secs

[catohagen]

Maybe not related to this issue, but this varying lag in the interface can also be related to Win10, as V12 running on a Win7 machine does not have *any* lag at all.
But V12 and V13 running on Win10 (and on a beefier pc), the lag is noticable.

[Mjbanderson]

Maybe not related to this issue, but this varying lag in the interface can also be related to Win10, as V12 running on a Win7 machine does not have *any* lag at all.
But V12 and V13 running on Win10 (and on a beefier pc), the lag is noticable.

Agreed.
We would still be running Windows 7 on our programming computers if it was still supported by Microsoft, but it isn't...so we arent.
I remember the copy/paste function pasting before my finger even left the 'V' key.

[George Woyansky]

Agreed.
We would still be running Windows 7 on our programming computers if it was still supported by Microsoft, but it isn't...so we arent.
I remember the copy/paste function pasting before my finger even left the 'V' key.

The good old days!

Now it's like :
User pressed CTRL-C
check to see if the user is authenticated
run Anti-Virus scan on keyboard interface to make sure there's not a remote key logger installed
Run anti-phishing scan
Validate identity of user in domain to make sure user has rights to copy things to the clipboard
Yes, user is allowed to press CTRL-C after all
<Copy>

So much overhead because a bunch of pinheads have nothing better to do than sit around all day figuring out how to hack the rest of our computers and see if they can get people to buy them giftcards and call them with the numbers on them once they've stolen our information.

Performance degradation directly attributable to keeping us safe from ourselves.

[JeremyS]

Process dialog performance is a work in progress. It won't be in this next web update but should be in the one after that.