1. Subrat patra
  2. PowerBuilder
  3. Monday, 6 March 2023 11:56 AM UTC

Hi Team,

 

We have powerbuilder application which is build in PowerBuilder 2019R3 and database is MS SQL. In the development environment application is running perfectly ok, but when we deployed it either to QA or client environment its taking time. For example - After login, to open the main window its taking 16seconds in development environment, but in QA or production its taking approximately 1 minute. In some modules we are experiencing the unusual crashes also. If we take the same scenario/same data/same database then in development environment no crashes happening.

Please find below all other details.

1> Pb2019R3

2> MS SQL server

3> I have tried using PB.ini with accessibility 0.

4>  I have put the SQL trace also, as its working on dev environment, but not QA, so didnt get anything strange thing here.

5> Powerbuilder trace I put in the dev environement, not sure how to do the PB trace on other enviornment,if any suggestion please let me know.

 

Please suggest what are other things i need to check for the performance issue.

 

 

Regards

Subrat

Daryl Foster Accepted Answer Pending Moderation
  1. Tuesday, 7 March 2023 00:03 AM UTC
  2. PowerBuilder
  3. # 1

I recently had a application startup delay with our application written in PB2019R3.  It seems to be printer related.  I had my home printer set as the default printer in Windows 10, and when I was in the office, or when the printer wasn't turned on at home, the application took ages before it started displaying the first database retrieval.  I switched my default printer to the Microsoft PDF printer and now it works fine.  It seems like Powerbuilder wants to connect to the printer before it does anything datawindow related, and if it can't connect to the default printer it waits until it times out before continuing.

Comment
  1. Armeen Mazda @Appeon
  2. Tuesday, 7 March 2023 01:18 AM UTC
  1. Helpful
  1. Daryl Foster
  2. Tuesday, 7 March 2023 01:32 AM UTC
Thanks Armeen, we don't use the rich text control or terminal services. My problem seemed to be specifically datawindow/printer related.
  1. Helpful
  1. Chris Pollach @Appeon
  2. Tuesday, 7 March 2023 03:26 AM UTC
Hi Daryl;

This is critically important with DWO's as they get "all" their working fonts from the current default printer. If a default printer is not found OR the default printer does not have the desired fonts that the DWOs require, the PBVM will "dynamically try to synthesize them". This synthesis process is *extremely* CPU intensive and really slows every DWO rendering down *every* time any DWO tries to paint the area inside a DW Control. Thus, performance can degrade exponentially if these printer anomalies occur. Food for thought.

Regards ... Chris
  1. Helpful
There are no comments made yet.
Armeen Mazda @Appeon Accepted Answer Pending Moderation
  1. Monday, 6 March 2023 17:34 PM UTC
  2. PowerBuilder
  3. # 2

Is the database and the PB app in same local area network?  The PB app should not be remotely accessing the database over Internet or that would cause this kind of problem.

Comment
There are no comments made yet.
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Monday, 6 March 2023 13:09 PM UTC
  2. PowerBuilder
  3. # 3

Hi Subrat;

  Perchance, are you running the App in production from a File Server & also then via RDT?

Regards... Chris 

Comment
  1. Chris Pollach @Appeon
  2. Monday, 6 March 2023 13:44 PM UTC
Then there are a few things to consider when running that way ..

1) Menu, Window, User Object, etc icons. If they are not the built-in ones, the the PBVM will keep constantly going back to the file server to fetch them.

2) the PB runtime DLLs could be constantly reloading from the file server.

3) RDT itself could be the overhead issue.

4) Network latency in production could be quite high. Numerous network segments being traversed, etc.

5) the production SS Server may need further optimization.

6) the volume of production data could make queries longer. The SS "Statistics" may need to be reset.

HTH

Regards... Chris
  1. Helpful 1
  1. Subrat patra
  2. Monday, 6 March 2023 14:01 PM UTC
Hi Chris, Network related issues i dont think. because we have only 1-2 QA developer are there and its for only one version of app .And the users in atlanta and chicago both are facing the issue.

2> All my PBDS and exe are on the same server.



any other suggestion.





  1. Helpful
  1. Chris Pollach @Appeon
  2. Monday, 6 March 2023 16:55 PM UTC
Hi Subrat;

Those were just suggestions on where to look for many anomalies in production vs development that could be affecting your PB Apps performance.

Regards ... Chris
  1. Helpful
There are no comments made yet.
John Raghanti Accepted Answer Pending Moderation
  1. Monday, 6 March 2023 12:46 PM UTC
  2. PowerBuilder
  3. # 4

Hi, I get the feeling from your question that there is an unresolved path that windows is trying to resolve and is eventually timing out. Do you have any hardcoded paths in your code or stored in the database that don't exist on the affected machines?

Paths like: \\server\application\deployment\src.ini or

c:\program files (x86)\mypath\myfile.txt ?

Comment
  1. Subrat patra
  2. Monday, 6 March 2023 12:50 PM UTC
Hi John,

No, we dont have anything like that.

Regards

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