1. Marco Armbruster
  2. PowerBuilder
  3. Thursday, 27 June 2024 17:27 PM UTC

Hello,

we migrated our app from PB11 to PB2022 R2 3356 a few month ago. 

Some (not all) of our users are complaining about the new speed of our app.

The more windows are opened, the slower the entire software becomes.

If there is one window open, it takes two seconds to open a special test window.

If there a two windows open, it takes 15 seconds to open the same test window again.

Another problem: If the user clicks on a other app in the task bar windows switches to this app immediately without any loss of time. Trying to get back to the Powerbuilder app takes a longer time. This time depends on the number of opened windows in the app. It seems that nothing is happening and after a while the main window of the app appears. While waitung the cpu goes up. This only happens at a few customer, but than on all pc. 

I checked the task manager, GDI, memory, cpu. No abnormalities

Any idea?

Thanks for your advice/help

Marco

Marco Armbruster Accepted Answer Pending Moderation
  1. Friday, 28 June 2024 08:50 AM UTC
  2. PowerBuilder
  3. # 1

one thing I should mention. It´s just a thought...

In older times there was a speed problem when running Sybase Central (V11) and PB11.5 app at the same time.

As long as the scjview.exe was running the response time of the app was horrible slow.

It feels similar now...

Comment
There are no comments made yet.
Miguel Leeuwe Accepted Answer Pending Moderation
  1. Friday, 28 June 2024 02:05 AM UTC
  2. PowerBuilder
  3. # 2

Do any of these problematic pc have touch screen ability in windows?

If so, try deactivating it in windows, just to test if there[s a difference.

Comment
  1. Marco Armbruster
  2. Friday, 28 June 2024 07:39 AM UTC
There are no touch screens at all.

Checked to have no drivers installed or activated.

Thx for your advice
  1. Helpful 1
There are no comments made yet.
Arnd Schmidt Accepted Answer Pending Moderation
  1. Thursday, 27 June 2024 21:26 PM UTC
  2. PowerBuilder
  3. # 3

Hi Marco,

have you already checked the accessibility feature?

https://docs.appeon.com/pb2022/troubleshooting_guide/tr_134.html

hth .. Arnd

Comment
  1. Marco Armbruster
  2. Friday, 28 June 2024 07:40 AM UTC
No changes in behavior.

Same speed with or without pb.ini

Thx for your advice
  1. Helpful
There are no comments made yet.
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Thursday, 27 June 2024 17:48 PM UTC
  2. PowerBuilder
  3. # 4

Hi Marco;

  Can you tell us ...

  • MS-Windows version & build that the issue is happening with?
  • Are the App users running on real machines or VM's?
  • Is the App running native of via Citrix, RDP, etc?
  • Is the App compiled to P-Code or M-Code
  • Is the App 32 or 64 bit compiled?
  • What DBMS version & build is the App interacting with
  • What DB Client settings are being used (ie: all SQLCA settings being used)?

Regards .. Chris

Comment
  1. Marco Armbruster
  2. Friday, 28 June 2024 08:10 AM UTC
Hi Chris,



MS-Windows version & build that the issue is happening with?

-> Win10 Pro, Version 22H2, Build 19045.4509

-> But happening on Win11 too



Are the App users running on real machines or VM's?

-> real machine



Is the App running native of via Citrix, RDP, etc?

-> app is running local



Is the App compiled to P-Code or M-Code

-> P-Code



Is the App 32 or 64 bit compiled?

-> 32bit



What DBMS version & build is the App interacting with

-> SQL Anywhere 17.0.4.2182



What DB Client settings are being used (ie: all SQLCA settings being used)?

dbms = ODBC

dbparm = connectstring ='DRIVER=SQL Anywhere 17;SERVERNAME=demo3;DBN=FAB;DBF=FAB.DB;UID=xxx;PWD=xxx;COMMLINKS=TCPIP(HOST=LOCALHOST);COMPRESS=YES;DisableMultiRowFetch=NO;IdleTimeout=0;LivenessTimeout=0;Integrated=NO;Debug=NO'

sqlreturndata = 'SQL Anywhere'



We will update the database to version 17.0.11.7672 today.

  1. Helpful
  1. Chris Pollach @Appeon
  2. Friday, 28 June 2024 14:39 PM UTC
Hi Marco;

Also check ...

1) SQL tracing at the PB layer is OFF (no SQLCA.DBMS = "TRACE ODB" setting)

2) SQL tracing at the ODBC layer is OFF

3) Connection Pooling at the ODBC layer is ON.

Regards .. Chris
  1. Helpful
There are no comments made yet.
  • Page :
  • 1


There are no replies made for this question yet.
However, you are not allowed to reply to this question.
We use cookies which are necessary for the proper functioning of our websites. We also use cookies to analyze our traffic, improve your experience and provide social media features. If you continue to use this site, you consent to our use of cookies.