1. Richard Lynskey
  2. PowerBuilder
  3. Thursday, 13 June 2019

Is anyone else noticing that simply migrating an app from 12.6 to 2019 that the compiled apps are slow? I compiled an app in 12.6, then migrated the target to 2019 and compiled it there. A window in the 12.6 version that took 10 seconds to open takes 20 seconds in 2019. In some other areas I've seen as little as a 2 second increase using 2019. And during the beta, everything actually seemed to launch quicker than their 12.6 counterparts.

Is anyone else having any issues like this?

Who is viewing this page
Accepted Answer
Armeen Mazda Accepted Answer Pending Moderation
3
Votes
Undo

Many customers have upgraded to PB 2019.  Other than the issue I mentioned below, we are not aware of any widespread performance issues with PB 2019.

This could be caused by not deploying the UI theme runtime file pbtheme190.dll and pbjson190.dll (even if you are not using this feature).  When it is drawing the UI it is looking for this and that is slowing things down.

We are making enhancements in PB 2019 R2 so that if you aren't using the UI theme feature you won't need to deploy its runtime DLL.  In the meantime, you can work around the issue by copying these files over.

Comment
There are no comments made yet.
  1. Thursday, 13 June 2019
  2. PowerBuilder
  3. # Permalink
Christian Behrens Accepted Answer Pending Moderation
0
Votes
Undo

Hi all,

I'm having the same problem.
My application runs fine and fast when compiled with PB2017 R3.
But slow when compiled with PB2019.
Even a simple action like a row change in a datawindow (without retrieving any new child data) feels slow.

The application is connected to an Oracle DB using the native drivers.
(Just to say that the behaviour is not just in conjunction with MS SQL or OLE DB.)

I can confirm that this seems to be related to the executing host, maybe the operating system:
The slowness occurs on a Windows 10 (64 bit).
The same EXE when executed on my Windows 7 (64 bit) performs normally.
And the same application - when compiled with PB2017 R3 - runs perfectly smooth on the Windows 10 as well.

The application is compiled as 32 bit P-Code.

Any more ideas ?

Regards,
Chris

 

Comment
Hi Chris, I would suggest to open a support ticket. This doesn't sound like you are doing something incorrectly, at least not something obvious.
  1. Armeen Mazda
  2. Thursday, 12 September 2019
There are no comments made yet.
  1. Thursday, 12 September 2019
  2. PowerBuilder
  3. # 1
Brad Mettee Accepted Answer Pending Moderation
0
Votes
Undo

Roland mentioned a couple weeks ago that missing a PBTheme190.dll file (not sure if there are others) was causing issues even when themes weren't being used. 

Is your app exe running slowly on dev machine, or deployed machine? If deployed only, this would be easy to test.

 

Comment
Hi Brad et Al;

Yes, there is a known bug in PB2019 GA. Even though you are *not* using the new Theme feature or JSON processing in your applications. IF you do *not* deploy the " PBTheme190.dll" and "pbjson190.dll" DLL's with your PB app EXE. The EXE's will definitely run slower. Engineering is aware of the problem.

HTH

Regards ... Chris
  1. Chris Pollach
  2. Thursday, 12 September 2019
There are no comments made yet.
  1. Thursday, 12 September 2019
  2. PowerBuilder
  3. # 2
Brad Wery Accepted Answer Pending Moderation
0
Votes
Undo

Take a look at Roland's comment in this thread:

https://community.appeon.com/index.php/qna/q-a/themes-are-practically-useless-for-an-existing-mature-application/oldest#filter-sort

"I submitted a bug with themes. When your app does not use themes and you do not deploy PBTHEME190.DLL with your runtime, the app runs very slowly. Scrolling a grid datawindow is particularly slow."

It might not be the cause of your issue but it's worth ruling it out.

Good luck.

 

 

Comment
There are no comments made yet.
  1. Thursday, 12 September 2019
  2. PowerBuilder
  3. # 3
Peter Lorenz Accepted Answer Pending Moderation
0
Votes
Undo

I have the same now.

It seems to be a machine specific issue.

I'm compiling my Powerbuilder programs for years now via Jenkins on a Windows Server 2012 R2 and deploy the exes together with a bunch of DLLs.

This worked really fine for years now including Powerbuilder2017, 64x

 

Powerbuilder2019 behaves differently.

When I now deploy Powerbuild2019 exes (with the new set of DLLs: *190.DLL) to other machines than my own,

they are running very very slow ...

On my own machine they run just normally.

So, I assume, I'm missing a file (ore more) in the deployment.

But how du I find out which one(s) are missing?

 

The files I deploy together with the program are:

atl100.dll
libjcc.dll
libjtml.dll
libjutils.dll
libsybunic.dll
nlwnsck.dll
PBACC190.DLL
PBCMP190.DLL
pbcomrt190.DLL
pbdpl190.DLL
PBDWE190.DLL
pbdwr190.pbd
PBJAG190.DLL
PBjvm190.DLL
pbscr190.DLL
PBSHR190.DLL
PBSNC190.DLL
pbtra190.DLL
pbtrs190.DLL
PBUIS190.dll
PBVM190.DLL

 

any ideas?

 

Thanks in advance!

Peter

 

Comment
note to myself: yes, it seems so be the Sql Server connection
  1. Peter Lorenz
  2. Thursday, 12 September 2019
well, it might be the Version of the SQL Server Native Client..

My clients use Version 2011.110.2100.60 from 02.11.2012 -> slow...

I use Version 2011.110.7462.06 from 01.06.2018 -> normaly fast...

  1. Peter Lorenz
  2. Thursday, 12 September 2019
There are no comments made yet.
  1. Thursday, 12 September 2019
  2. PowerBuilder
  3. # 4
Chris Pollach Accepted Answer Pending Moderation
0
Votes
Undo

Hi Richard;

  FWIW:  I have not noticed any specific application performance issues in PB2017/2019 vs 12.6. However I did find one exception to that and, it seems to revolve around using the OLE-DB DB driver (very slow against SQL Server) in my testing and for some Appeon customers. However, changing the PB Apps to use either an  SNC or ODBC DB Client connection seems to cure that performance issue.

Regards ... Chris

 

Comment
There are no comments made yet.
  1. Thursday, 13 June 2019
  2. PowerBuilder
  3. # 5
Richard Lynskey Accepted Answer Pending Moderation
0
Votes
Undo

Alright, that basically answers my question then. If it's just me, I'm clearly doing something wrong. Thanks!

Comment
Try completely regenerating all the PBLs again and also test on another computer to make sure it is not something machine-specific.
  1. Armeen Mazda
  2. Thursday, 13 June 2019
That's basically what I intend to do. I've got a Windows 7 machine next to me I intend to try it on as well, and I'll take it and try it in 2017R3 as well just to compare.
  1. Richard Lynskey
  2. Friday, 14 June 2019
There are no comments made yet.
  1. Thursday, 13 June 2019
  2. PowerBuilder
  3. # 6
  • Page :
  • 1


There are no replies made for this question yet.
However, you are not allowed to reply to this question.