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

Resolved Window opening delay when applying Themes

  1. Issue
0
Votes
Undo
  1. David Peace (Powersoft)
    David Peace (Powersoft)
  2. PowerBuilder
  3. Monday, 20 November 2023 13:40 PM UTC

Hi Everyone

We are experiencing an issue after applying themes to a complex application. We are seeing a noticeable delay in window opening response times between no theme and a theme being applied. On some windows the opening delay is approximately 1 second. Admittedly the window is very busy and complex.

Looking at window resource monitor most of that extra delay is after the data has been retrieved (i.e. network traffic stops).

There is some overhead in our code in the DW constructor event but that only accounts for a small percentage of the delay.

In some instances the window goes completely black for a moment before rendering.

Has anyone else experienced performance issues?

 Thanks

David

*Edited* Just edited to draw attention to this, the performance issue has caused the customer to roll back the Themed version. It would be good to get some feedback.

  1. PowerBuilder
  2. Theme
SMTPClient.Message.Reset() does not clear the HTML...
Image in Resource File(.pbr) not showing when DW i...
Responses (3)
Armeen Mazda @Appeon
Armeen Mazda @Appeon Accepted Answer Pending Moderation
  1. Friday, 24 November 2023 02:35 AM UTC
  2. PowerBuilder
  3. # 1

Terminal services doesn't scale.  You need to throw more hardware at it.

Comment
Load more comments
Chris Pollach @Appeon
  1. Chris Pollach @Appeon
  2. Friday, 24 November 2023 15:17 PM UTC
The key would be to have your PS Apps avoid long queries and large result sets. ;-)
  1. Helpful
David Peace (Powersoft)
  1. David Peace (Powersoft)
  2. Monday, 27 November 2023 12:30 PM UTC
Yes, but this is a large old system, chnaging it now will require a lot of reworking the UI. This is part of a long project with many phases.
  1. Helpful
Armeen Mazda @Appeon
  1. Armeen Mazda @Appeon
  2. Monday, 27 November 2023 14:33 PM UTC
Hi David, Most customers can solve the latency issue by using PowerServerLabels without any major rewrite/redesign of your legacy code. See the performance tuning guide: https://docs.appeon.com/ps2022r2/Grouping_server_calls.html
  1. Helpful
There are no comments made yet.
Chris Pollach @Appeon
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Thursday, 23 November 2023 21:22 PM UTC
  2. PowerBuilder
  3. # 2

Hi David;

  From my own testing I am seeing about a .25 to .5 second delay in very busy window instantiation on my older machines but not on my new machines.

  My STD Framework opens all windows with almost no  control constructor or window open logic on those events. The window is defined as invisible by default is then made visible when a Post Open event occurs. With this architecture approach, I am not perceiving any opening delays (from the App user perspective). The key here is not perceivable or what I call "the illusion of response time" by design.  ;-)

  As a foot note, my older processor machines do seem to have a bit slower App execution. However, on my new Ryzen 5 & Ryzen 7 PCs I cannot tell at all. Just to give you a comparison, on my older PCs with the PB IDE, the STD Framework full builds are 4-5 minutes. On my Ryzen 7 a full build is 15-20 seconds. So I think that updating your older hardware with newer O/S's, Office, PB, PDF, etc software releases demands new hardware to offset it.  IMHO  HTH

Regards ... Chris 

Comment
Load more comments
Chris Pollach @Appeon
  1. Chris Pollach @Appeon
  2. Friday, 24 November 2023 12:20 PM UTC
Hi Andreas;

That's a good point about which core is being loaded up.

@David: my STD Framework can change the Apps execution on various cores. If you're finding that the O/S is defaulting to an overloaded core, this code might help.

Regards ... Chris
  1. Helpful
David Peace (Powersoft)
  1. David Peace (Powersoft)
  2. Monday, 27 November 2023 12:40 PM UTC
Yes, it is a good point. Monitoring the cores I see one core hit 75% usage at the timeof rendering the screen. None of the cores are maxing out. Disk IO is not at all high and memory is good.



"The window is defined as invisible by default is then made visible when a Post Open event occurs", this has saved a small amountof time so thanks for that. It's going to be a lot of small gains on this one.
  1. Helpful
David Peace (Powersoft)
  1. David Peace (Powersoft)
  2. Friday, 2 February 2024 12:04 PM UTC
Just thought I would pick up on this one, we are refactoring the screen significantly to resolve the performance hit. Thanks for all the contributions and help.
  1. Helpful
There are no comments made yet.
David Peace (Powersoft)
David Peace (Powersoft) Accepted Answer Pending Moderation
  1. Thursday, 23 November 2023 17:32 PM UTC
  2. PowerBuilder
  3. # 3

Bump to try and get a response

Comment
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.