• You are here:  
  • Home
  • Q&A
  • Q&A
  • PowerBuilder
  • Opening a window in Powerbuilder takes a long time

Subscribe via RSS
Toggle Submenu
  1. Categories
  2. Recent
  3. Tags
View Replies (5)

Resolved Opening a window in Powerbuilder takes a long time

  1. How-to
0
Votes
Undo
  1. Ferdinand Fischer
    Ferdinand Fischer
  2. PowerBuilder
  3. Monday, 16 July 2018 16:38 PM UTC

When i open a window with many command buttons (ca 40) powerbuilder takes really long - at least 30 seconds -until i can use it again.

i can literally watch the obejcts being drwan.

The same  happens whenever the buttons need to be drawn.

I compared it with a  colleaguecolleague colleague's laptop, which is the same model, and it was a lot faster.

 

Is there way to find out what makes my powerbuilder slower?

 

 Edit:

The problem is in the IDE not the application.

Information:

Powerbuilder 10.5.1  Build 6662

CPU i7 7820hq

 

Thanks 

Ferdinand

 

Can not load Sybase.Powerbuilder.Datasource.DB
Datawindow not getting displayed in window.
Responses (5)
Chris Pollach @Appeon
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Tuesday, 17 July 2018 13:58 PM UTC
  2. PowerBuilder
  3. # 1

Hi Ferdinand;

  A few other things that I just thought of:

  1. How does your PC vary from your co-workers? Say for example in the robustness of your video card.
  2. PB and the DWO utilize their drawing based on the default printer and thus its related fonts. I wonder if your default printer is the culprit. See what your co-workers printer settings are.

HTH

Regards ... Chris

Comment
Ferdinand Fischer
  1. Ferdinand Fischer
  2. Tuesday, 17 July 2018 14:15 PM UTC
Hi Chris,

1. We have all the same configuration. We have a NVIDIA Quadro M1200. Even if i force it to use the Nvide card over the context menu it doesnt get better.

2.We have the same default printer. But how is the drawing of the grid related to the printer? I dont get that.
  1. Helpful
Chris Pollach @Appeon
  1. Chris Pollach @Appeon
  2. Tuesday, 17 July 2018 14:38 PM UTC
Sounds like the basics then are the same. I did not know if you had any DataWindow(s) on your Window instance. Its the DWO`s that utilize the default printer settings. Sounds like this is not your issue then but, just wanted to make sure.



Very weird!
  1. Helpful
There are no comments made yet.
Alfredo Aldama
Alfredo Aldama Accepted Answer Pending Moderation
  1. Tuesday, 17 July 2018 03:37 AM UTC
  2. PowerBuilder
  3. # 2

 

 

Hi,

 

I read the bug that you mention, so I did a test: a window with 60 buttons,

The response time less than 1 second.

My tip
Verify that you have not activated any trace.

Verify the events in which you have code.

Check in events that can be executed before the opening of the window, for example in constructor events or the activate event of the window

 

 

 

Regards !

Comment
There are no comments made yet.
Ferdinand Fischer
Ferdinand Fischer Accepted Answer Pending Moderation
  1. Monday, 16 July 2018 17:22 PM UTC
  2. PowerBuilder
  3. # 3

--

Comment
There are no comments made yet.
Chris Pollach @Appeon
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Monday, 16 July 2018 17:12 PM UTC
  2. PowerBuilder
  3. # 4

Hi Ferdinand;

  That sounds very unusual!

Can you tell us:

  1. Does your App use any frameworks (ie: PFC)
  2. What DBMS version are you using?
  3. What DB client is the App using to connect to the DBMS?
  4. What MS-Windows version are you using?
  5. Are you on a real PC vs a VM?

etc

Regards ... Chris

 

Comment
Ferdinand Fischer
  1. Ferdinand Fischer
  2. Monday, 16 July 2018 17:51 PM UTC
Hi Chris,



1. Does your App use any frameworks (ie: PFC)

Kind of. We have our own base classes.

2. What DBMS version are you using?

SQL Anywhere 12

3. What DB client is the App using to connect to the DBMS?

ODBC

4. What MS-Windows version are you using?

Windows 10 Pro

5. Are you on a real PC vs a VM?

Real









  1. Helpful
Chris Pollach @Appeon
  1. Chris Pollach @Appeon
  2. Monday, 16 July 2018 18:41 PM UTC
It could be an issue with W10 and your old version 10.x version of PowerBuilder. W10 compliance was only achieved last year under the Appeon PB2017 version released last July of 2017.



A quick "sanity check" could be to download a trial version ( https://www.appeon.com/freetrial?product=pb ) of PB2017R2. It can co-exist with older PB releases. Then see if your App behaves properly under W10 with the new PB version. If it does work OK with PB2017R2, then its something with your PB 10.x version or installation. If you encounter the same performance issues with PB2017, then you'll have to dig deeper into PB 10.x's interactions with W10. In particular the way W10 is set-up for you or other 3rd party software that might be interfering.



Food for thought.

  1. Helpful
Ferdinand Fischer
  1. Ferdinand Fischer
  2. Monday, 16 July 2018 20:31 PM UTC
Setup:

Alignment Grid

X:4

Y:4

My WIndow:

60 Command buttons

4 group boxes

1 multiline edit

width 4859

height 2660



After a few tests i have come up with these numbers:



OS Powerbuilder time Show Grid

Windows 10 PB 10.5.1 10s yes

Windows 10 PB 2017 R2 3,4s yes

Windows 10 PB 10.5.1 instant no

Windows 10 PB 2017 R2 instant no



Neither compatibility mode nor the base class make a difference.

There is big difference between the old and the new Powerbuilder.

But the important fact ist, that all the time is spent drawing the grid on the empty window.

Once i deactivated the grid, i couldn measure the time anymore.

It doesnt even matter if you can see the grid or not.

in conclusion the the laoding time is increased by adding more objects or increasing width/height.

That is the same in the new Powerbuilder.





  1. Helpful
There are no comments made yet.
Chris Pollach @Appeon
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Monday, 16 July 2018 16:52 PM UTC
  2. PowerBuilder
  3. # 5

Hi Ferdinand;

      My suggestion is to run your App through the "Application Profiler" built into the PB IDE and the same for your co-worker and the compare the top worst areas of poor performance. That should hopefully give you some idea on where to look into your App's system for these issues.

HTH

Regards ... Chris

Comment
Load more comments
Armeen Mazda @Appeon
  1. Armeen Mazda @Appeon
  2. Tuesday, 17 July 2018 00:20 AM UTC
Hi Bjarne,



Based on Ferdinand's testing it seems PB 2107 R2 is more than 2X faster than PB 10. So it looks like some improvements have been made in this regards. Some of the slowness may be design issues from Sybase days rather than a bug that is quick fix. But regardless, if you are still experiencing unbearably slowness with PB 2017 R2 please report a new bug here: https://www.appeon.com/standardsupport/newbug



Thanks,

Armeen
  1. Helpful
Ferdinand Fischer
  1. Ferdinand Fischer
  2. Tuesday, 17 July 2018 06:38 AM UTC
Hi Armeen,



is there a way to profile the IDE during the drawing of the of the Grid.

As said my colleagues dont have this problem and i would like to find out what makes it on my pc so slow.
  1. Helpful
Brad Mettee
  1. Brad Mettee
  2. Tuesday, 17 July 2018 13:28 PM UTC
What video card and drivers are you and your colleague using? Windows 10 uses advanced video functions to do repaints in standard GUI as well as graphics heavy app (3d modelers, games). If your driver is outdated, or the video card is too old, you might be seeing the results of redraws taking a significantly longer time than with newer drivers/hardware.



You might also consider comparing your PB.INI files (in pb10, it's in "c:\users\\AppData\local\VirtualStore\Program Files (x86)\Sybase\Powerbuilder 10.0", in PB17 it's "c:\users\\AppData\local\Appeon\Powerbuilder 17.0") to see what's different between your machines.
  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.