1. Bjarne Anker
  2. PowerBuilder
  3. Tuesday, 30 January 2018 18:01 PM



One of our customers are experiencing some weird issues regarding the performance..

They have Windows Server 2012 R2 databaseserver, running one SA16 database which is approx 10 Gb. 32 Rb RAM. Typically 18-20 connections.

The terminalserver is Windows 2008 R2. Also 32 Gb RAM. Often it´s just 7-8 users running our application.

Our application is located on a fileserver running Windows Server 2012R2, and the users run our application (PB2017) from a shortcut to the exe-file on a mapped network drive on the fileserver.

Most of the time it works great, but every now and then the users experience extreme drop in performance in our application.

One user reported that it took 4-5 seconds just to show the list in a dropdown datawindow, which is populated with data on pfc_postopen() of the form.

Other tasks can take over 5 times the amount of time compared to normal behavior.

The terminalserver is restarted every night with a fresh master image, and is just running our application and Office 2016.

When we connect to the users computer or the terminal server, we rarely see this issue.

The performance of the databaseserver is never a problem. 11/32 Gb memory used and never over 25-30% CPU usage.


Can this old version of Windows Server 2008 on the terminal server be the issue?

Is there anything we can monitor over time to catch the behavior and see what causes it?


Anyone has similar experience as this? And perhaps some leads on where to start looking?

We have to help our customers IT-supplier to get to the bottom of this.




Bjarne Anker

Govinda Lopez @Appeon Accepted Answer Pending Moderation
  1. Wednesday, 31 January 2018 16:31 PM
  2. PowerBuilder
  3. # 1

Hi Bjarne Anker,


I would recommend you, first of all, checking on the system messages from your Windows Servers to see if there was any alert thrown from the OS or Database. Sometimes there can be some problems in the communication between servers that could cause this.

If everything seems fine, then I would recommend you doing a trace and profiling your application.

You use tracing and profiling to debug and tune an application. When you run an application, you can generate an execution trace file. You use the trace file to create a profile of your application.

The profile shows you which functions and events were called by which other functions and events, how often they were called, when garbage collection occurred, when objects were created and destroyed, and how long each activity took to complete. This information will help you identify areas that you should rewrite to improve performance and find errors in the application's logic.

Three profiling tools are available on the Tools tab in the New dialog box: Class View, Routine View, and Trace View. To use any of these tools, you must first create a trace file by turning tracing and profiling on in the System Options dialog box and running your application. You can also create a trace file by adding profiling functions to your application.

You can find more information about this on the PowerBuilder help files.


I hope this helps.



Hi Govinda.


I've done a lot of profiling in our application, but no significant issues are found.


The customer's IT-supplier will now try to upgrade the terminal servers to Windows Server 2012 R2.

They think that that one of the Windows Updates last fall has started these problems.

I will comment this thread when it is done and testing is done.





  1. Bjarne Anker
  2. Thursday, 1 February 2018 09:18 AM
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.