1. Olan Knight
  2. PowerBuilder
  3. Wednesday, 14 April 2021 03:08 PM UTC

I finally identified the cause of the performance slowdown in both PBv12 and PB2019R3. The problem is the DBPARM option "DisableBind=1".

Removing the DISABLEBIND=1 from the DBPARMS resolves the issue in both PBv12.1 and PB2019R3.
 
Solution:
Change the DBPARM
   from this:
        SQLCA.DBParm = "DelimitIdentifier='No', DisableBind=1, PackageProcs=1, STATICBIND=1"
   to this:
         SQLCA.DBParm = "DelimitIdentifier='No', PackageProcs=1, StaticBind=1"


Olan

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~



PBv12.1 b7055 & PB2019R3 b2670
Oracle 12C
Windows 64 bit platform


The main function of our primary app is to generate invoices. All of the code is internal to Powbuider, using PB script, DWs, and embedded SQL.  We have migrated this huge app to 2019R3 and like it, but we've run into a show-stopper:  the 2019R3 version of the app is 5 times slower than the PBv12.1 version when generating invoices.

In a desperate attempt to gain processing speed, I have compiled the app into Machine Code, i.e. DLLs instead of PBDs. We tested the DLL version of the 2019R3 app against the PBD version ofthe PBv12.1 app, and the 12.1 version was 5 times faster. Five large invoices (a very small subset) required 7.1 seconds in v12.1 and required 29.7 seconds in 2019R3. We tested with the exact same code on the exact same platform using the same invoices running against the same database.

I've no idea why 2019R3 is so much slower, and I really did not expect that to be the case. But it is what it is, and it's a show-stopper. We will not deploy the 2019R3 version of the code until the processing performance matches that of PBv12.1, or at least get close to it.

This is a shame, because 2019R3 is the preferred version, and the code it creates works with the Windows 2019 server under Citrix, and the 12.1 version does NOT. So....we'd LOVE to migrate, but cannot do so at this time.


Q1: Does anyone have any suggestions on how to speed up the processing of 2019R3?


I expected the DLL version of the application to be significantly faster than the PCODE version, yet the  performance of both versions of the code was nearly identical.
Q2:  Was my expectation unrealistic?

Q3:  Does having the "Enable DEBUG Symbol" option checked make any difference?


Responses (10)
  1. Likes
  2. Latest
  3. Oldest
Loading...

Find Questions by Tag

.EXE .NET 6.0 .NET Assembly .NET Core 3.1 .NET Core Framework .NET DataStore .NET Std Framework 32-bit 64-bit ADO.NET AEM AI Algorithm Amazon AWS Android Apache API APK App Store App Store (Apple) Appeon Workspace Appeon Xcelerator Plug-in Architecture Array ASE Asynchronous Methods Authentication AutoBuild AutoCompiler Automated Testing Automation AutoScript Azure Barcode Base64 Batch BigData BLOB Branch & Merge Browser Bug Build Button C# C# Class Importer C# Editor C# Model generator Calendar Camera Certificate Chrome Citrix Class Client Client/Server Cloud Cluster Collection COM Command Line Compiler Compression Computed Field Configuration Controls Cookies Cordova Crash Cross-Platform Crosstab CSharpAssembly CSharpObject CSS CSV Cursor Data Database Database Driver Database Painter Database Profile Database Provider DataObject DataSource DataStore DataStore (C#) DataStore (PS) DataType DataWindow DATE DATETIME DB2 Debug Debugger Debugging Deployment Design DLL DO-WHILE Dockable Docker Documentation DOUBLE Download DragDrop Edge Edit Style Editor Elevate Conference Email Embedded SQL Emulator Encoding Encryption Enhancement Request Entity Entity Framework ERP Error Event Event Handler Event Handling Excel Exception Export Expression External Functions F# Field File File Access Filter Firefox Firewall Font FOR-NEXT Foreground Format Function Garbage Collection GeoLocation Git Graph HANA Hash Header HTML/5 HTTP/S HTTPClient Icon IDE Identity IIS IMAPI Import InfoMaker Inheritance Installation Integer IntelliSense Interface Internet Internet Explorer iOS IPA iPad iPhone IWA J# Java JavaScript JBoss JDBC JOIN JSON JSONGenerator JSONParser Kestrel Label Lambda Large File LDAP Library License LINQ Linux OS Load Balancing Localization Localized PBVM Log In Log Out Logging LONG LONGLONG macOS MAPI Maps MDI Memory Memory Leak Menu Merge MessageBox Messagging Method Migration MIME TYPE Mobile Model ModelStore ModelStore (C#) MSOLEDBSQL Multi Threading MVC MySQL n-Tier Namespace NativePDF NVO OAuth ODATA ODBC Office Offline OLE OLEDB Online Open Source OpenAPI OpenSSL Oracle OrcaScript Other Outlook Output Package Parameter Patch PayPal PB Classic PB Native PB.NET PBC PBD PBDOM PBG PBJVM PBL PBNI PBORCA PBVM PBX PDF Performance Permission PFC Picture Pipeline Play Store (Google) Plugin Popup Port POST PostgreSQL PowerBuilder PowerBuilder (Appeon) PowerBuilder (SAP) PowerBuilder Compiler PowerBuilder Runtime PowerClient PowerScript (PS) PowerScript IDE PowerScript Migrator PowerServer PowerServer Mobile PowerServer Toolkit PowerServer Web PowerServerLabel Print Properties Proxy Publish PULL PUSH Query Regression Release Renew Resize Response REST Retrieve RibbonBar RibbonBar Builder Rich Text Roadmap RPC Runtime Packager SaaS Scaffolding Script SDI SDK Security Server Service Session Single Sign-on Size SMTP SMTPClient SnapDevelop SOAP Sort Source Code Speech Recognition SQL SQL Anywhere SQL Server SqlBuilder SqlExecutor SQLite SqlModelMapper Storage Stored Procedure Subscription SVN Swagger Syntax TabbedBar TabbedView Tablet TabPage Target TE Control Testing Text TFS Theme TIME Timer TLS/SSL Tomcat TortoiseGit TortoiseSVN Transaction Transparency Trial Trigger TRY-CATCH TX Control Type UI ULONG UltraLite Uninstall Unit Test Unit Testing UNIX OS Update Upgrade Upload URL User Center User Object UWP Validation VARCHAR Variable Versioning Visual Studio Visual Studio Code VM Voice Warning WCF Web API Web Extensions Web Service WebBrowser WebForms WebLogic WebSphere WildFly WinAPI Window Windows OS WinForms Wizard Workgroup Workspace WPF XCODE XHTML XML Zoom

Helpful?

If a reply or comment is helpful for you, please don’t hesitate to click the Helpful button. This action is further confirmation of their invaluable contribution to the Appeon Community.