VL-IDE slow

[atostaine]

Latest EPC's, V14SP2, High end PC's, SSD's, etc.

Two identical PC's, the IDE has been getting slower and slower. It can take 30-45 seconds to save a field. Is there any reorg or cleanup we can perform on the PC's?

Thanks, Art

[LANSAGuru]

Art,

Someone told me that putting the power profile to Maximum or High Performance would help here. It seemed to, but on my machine with a local IDE it can seem a bit sluggish depending on what I am doing regardless of this setting.

If for instance you have a VL Web Page with many Views attached (30+) it can take a long time to render and open up and particularly SAVING is very slow. I assume this has to do with saving to the SQL Database and the power settings affect this somehow.

So try setting to power settings to not try and save power and see if that helps at all, and report back here for the benefit of others. I am curious how much this helps others.

Thanks,
Paul

[atostaine]

I changed to high performance, quick review it's still taking awhile to close a large VL-FORM, no save. Compiles are fast BTW, it's just the IDE.

Hitting the Up button in the details tab is taking over 1 minute while IDE is frozen.

[soa]

I am experiencing poorer performance from the IDE over the last couple of release. Often typing a letter to start a command or variable name will cause a lockup of several seconds before it jumps back to life.

[atostaine]

This has happened to me also. When Hamad did a go to assist it wouldn’t do it.

[dannyoorburg]

Hitting the Up button in the details tab is taking over 1 minute while IDE is frozen

That can't possibly be acceptable in any way.

It'll have something to do with whatever is open in the IDE at the time. A lot of code runs when the focus moves to a new component. Designer, detailer, outliner and all the ribbon sheets respond to the new focus component.

But that should NEVER take that long. If you can consistently reproduce it I would take it up with support.

Danny

[pkoopmanpk]

I changed to high performance, quick review it's still taking awhile to close a large VL-FORM, no save. Compiles are fast BTW, it's just the IDE.

Hitting the Up button in the details tab is taking over 1 minute while IDE is frozen.

That's exactly what we are experiencing. Closing complex forms and reusable parts, with no saving, takes up to 2 minutes. It was driving me crazy.

We did a log with Microsoft tool "Proces Monitor", while closing a large RUP.

There is a lot of communication to the MS SQL Express repository, after which the IDE seems to go to sleep for several seconds. Or it takes the repository a long time to answer.

[atostaine]

Yes. Just closing an RP takes several minutes.

On my customer DEV PC the only other open windows I have are an IBM iACS 5250 session. No browser or anything else.

I’ll submit an incident

[atostaine]

I submitted an incident. Here is the video I sent. Opening an RP is quick, but then closing it takes 30+ seconds.

https://youtu.be/dfP4qmYjSsU

[atostaine]

If you are having this problem please submit it to support. I hear it's a known issue.

[pkoopmanpk]

If you are having this problem please submit it to support. I hear it's a known issue.

Thank you. I submitted our problem to support.

[Theo de Bruin]

- Can you check the ODBC driver version that you use ?
- Is there logging or tracing enabled in your ODBC driver, or in X_LANSA.PRO?

>> It seems the SQL Native client version 11 works better than other ODBC drivers, so I would suggest you to try this out!

[pkoopmanpk]

The suggestion to use the SQL Native client version 11 is a good start.

The time for the source that took nearly 2 minutes to close with ODBC Driver 11 for SQL server, went down to 40 seconds.
On a second PC with ODBC driver 13, it also went down from 1 minute to 40 seconds.

[dannyoorburg]

Did you talk to support? I'm pretty sure there's a patch available addressing the time it takes to close a component...

Cheers,
Danny

[pkoopmanpk]

Yes we did, EPC 142060 is on our todo list.

[atostaine]

Yes we have the patch and it solved the problem closing components.

We still have other slowness issues that I need to submit those

[LANSAfolks]

I am using EPC142040 and also have the same issue where the IDE runs incredibly slow when working with large objects (3000+ lines of code). Also when working with objects that have a large number of dependencies via inheritance etc. What I see is that the CPU core running LANSA.EXE saturates and keeps saturated for long periods of time. In my case, compiles take up to a minute and sometimes more. Closing objects can also take minutes, with the CPU core being saturated all that time. I suspect this issue is a function of the complexity of the components being worked on, as well as something in the IDE that's eating up a lot of CPU cycles.

This slowness is easily recognized in V14SP2, whereas V12 and V13 run much faster. I read that EPC142060 has a solution for closing objects. Has anyone tried that EPC? Is your IDE stable post EPC142060? I still get a LANSA.DMP crash once in a while when opening, closing or compiling objects at EPC142040. So I am curious as to whether EPC 142060 has any IDE stability fixes too?

[atostaine]

I just installed, EPC142060, the slowness closing is still there. I have a hotfix that worked when I was on EPC142030 but I don't know if I can apply it now that I'm on 142060. I'm going to check with support.

[atostaine]

Support told me the hotfix I have is for EPC 142060. I had it working with EPC142030 but they say that's not supported.

[LANSAfolks]

OK, so there's a hotfix for EPC142060.
Not keen on installing hotfixes (unless I have to). Will have to wait for the next EPC in this case.
I am much more concerned about the IDE crashes I'm getting at EPC142040. I had at least 3 crashes today at different times e.g. when editing a pop-up menu item, or when changing the screen design of a reusable part.