Slow User Interface with PB 12.6

[Former Member]

I just loaded up PB 12.6 and the first thing I noticed is that my applications seem to run exceedingly slow when running from the Classic IDE environment.  The compiled code runs lightening fast, but it's ridiculously slow when running directly from the IDE.  I haven't really had a chance to dig into what might cause it, but I'm wondering if anyone else has experienced this.

[Former Member · Accepted solution]

I've figured out what was going on and fixed it!

The behavior seems to have been caused by the PBDebug Tracing system option which appears to have been active by default when I installed PB12.6.  After deactivating that feature on the system options dialog, everything seems to be all good now.

[roy_shang]

Hi Kevin,

I have checked the PB source code. We did not set the PBDebug default value to true.

This value is keep in PB.ini. And it did not change after your PB migration .

If you have set this option in PB12. You will get the same option in PB12.6.

Best Regards

Roy

[Former Member]

Hi Roy,

Thanks for checking on that for us.  I don't recall altering that setting, but I suppose I must have done so. 

Kevin

[Former Member]

Hi Kevin;

1) What version of PB are you upgrading from?

2) What version of MS-Windows are you using?

3) What DBMS are you connecting to.

4) After migrating to PB 12.6 - Did you optimize your PBL's?

Regards ... Chris

[Former Member]

I'm upgrading from 12.0, the workstation is running Windows 8 and MS SQL server.

I have not optimized the PBL's.  But I'll give that a try and let you know the behavior improves.

[Former Member]

FWIW: PB 12.6 is lightening fast for me but , all my PC's are still W7.

[Former Member]

Optimizing the PBL's seems to have helped some, but not a lot.  The application still runs stupid slow from the IDE, but really fast when it's compiled.  It's not a show stopper, just a little aggravating.

[Former Member]

Hi Kevin;

  Just for my interest sake ...  Are you compiling to P-Code or M-Code?

Regards ... Chris

PS: It could be good old W8. I'm waiting for W10!   

[Former Member]

Hi Chris,

I'm compiling to P-Code.

Love the W 10 pic.  I will have to use that myself.

When I get time, I'll try to load PB 12.0 on the Win8 machine and see how it does.

Thanks for the optimizing tip though, it did make a difference.

Kevin

[Former Member]

Excellent news ... Glad that you had some improvement!  

[Former Member]

The Win8 method for finding files may have changed. There might be a file it is hunting for and having trouble finding. It could be a file used only by the IDE.

Process Explorer can be used to see what files are being opened.

[Former Member]

Kevin,

Any chance you have the PBDebug tracing turned on?

Tools > System Options > General > Enable PBDebug Tracing

That would make the app run very slowly, for sure.

-Paul-

[Former Member]

Nope, I made sure that we're not in debug mode.  It's not just a little slower, it's stupid slow.  It takes more than two minutes to open a fairly light window that opens instantly when running from the compiled exe.  Everything works, it's just waaaaay slow. 

[Former Member]

Hi Kevin;

  You are talking about PB Classic right ... not PB.Net?

Regards ... Chris

[Former Member]

Correct.  PB 12.6 Classic running on Windows 8.  I'm going to try loading 12.0 on the same workstation to verify that it's not just PB in general.  Everything else works fine on the new workstation, including the compiled versions of PB apps.

[Former Member]

This will be a very interesting comparison for this issue!  

[Former Member]

So, after testing, it turns out that PB 12.0 works perfectly on the same workstation. 

When using 12.0 classic, the application runs fine through the IDE or compiled. 

However, with 12.6, the application runs ridiculously slow when initiated from the IDE, but super fast when run from the compiled exe. 

Same workstation, same code.  It's not a critical issue, but it is a bit aggravating.

[Former Member]

WOW ... Sounds like it would be very worthwhile to open up an incident (case) with SAP technical support on this one!

[Former Member]

Yeah, it's beginning to look like I'll have to open an incident.  I can't find anything that's causing the behavior.