Performance Tips and Tricks With ABL

ABL Performance Tips and Tricks
OpenEdge Developer’s Corner
Peter Judge
Principal Software Engineer
1 © 2009 Progress Software Corporation
Wherefore art thou, performance?
As important as stability, features, quality

Affected by
• Changing user counts, data, activity, traffic
• Application design & programming techniques
Different functionality = different needs
What determines good performance?
• Using the available resources efficiently
PSC Confidential
Better performance improves user satisfaction
http://www.gapingvoid.com/Moveable_Type/archives/003955.html
What can I do about it?
Software upgrades vs. hardware

upgrades
• Hardware faster, cheaper over time
Does faster hardware make you lazy?
You can only change what you control
• System configuration
Design & code for performance
• Don’t go overboard
• Don’t make things worse
Test & measure
PSC Confidential
Agenda
Coding for performance

Testing & measurement
Deployment & runtime considerations
Coding design
Good design is necessary

• Can have performance cost
• Classes generally faster than procedures
Consider caching
“Warehouse” into ProDataSets for
reporting
• Don’t try to do it all with one FOR EACH
PSC Confidential
Green coding
The fastest code is no code at all

Clean up after yourself
• Manage widgets using WIDGET-POOL
• Store references for deletion
Define statically, access dynamically
• Reuse what you can
Only get the data you need
• Filtered data for UI
Data across the network
Network typically major bottleneck

• Makes other performance problems
worse
Number of roundtrips
• Making AppServer connection has
cost
Data volume per roundtrip
Data per trip
Network topography has impact …

… but usually out of our control
PSC Confidential
Reduce data volume
Put your temp-tables on a diet

• Use MIN-SCHEMA-MARSHAL or NO-SCHEMA-
MARSHAL
– Stay away from RCODE-INFO
• Use transport temp-tables
• Use enumerations to compress data
Compression
• -mc (message compression)
No deep copies
define temp-table ttData ...
run populateData (output table ttData).

run visualiseData (input table ttData).
run getChanges (output table ttData).
run saveChanges (input table ttData).

h = buffer ttData:handle.
run populateData (output h).

run visualiseData (input h).
run getChanges (output h).
run saveChanges (input h).
PSC Confidential
No deep copies (2)
run populateData (output table ttData).

run visualiseData (input table ttData).
run getChanges (output table ttData).
run saveChanges (input table ttData).
run populateData (output table ttData by-reference).

run visualiseData (input table ttData by-reference).
run getChanges (output table ttData by-reference).
run saveChanges (input table ttData by-reference).
Understand how indexes work
Understand index selection rules

• Take care with OR in WHERE clause
• Also BY clause
Confirm actual indexes used

• COMPILE ... XREF
• INDEX-INFORMATION attribute
Know your indexes
PSC Confidential
Sequences
find counters where

counters.seq_name = “cust_num”
exclusive-lock no-wait no-error.
/* check lock & wait status; act accordingly */
create customer.
assign customer.cust-num = counters.value
counters.value = counters.value + 1
...
create customer.
assign customer.cust-num = next-value(seq_cust_num)
...
Unique values (when order doesn’t matter)
create customer.
assign customer.id = string(next-value(seq_table_id),
“9999999”)
...
create customer.
assign customer.id = guid()
...
PSC Confidential
Arrays faster than delimited lists
cDelim = “,”. /* or CHR(3) or | or ... */

cList = “item1” + cDelim + “item2” + cDelim
+ ... + “itemN”.
do i = 1 to num-entries(cList, cDelim):
cEntry = entry(i, cList, cDelim).
cArray[1] = “item1”.
cArray[2] = “item2”.
cArray[n] = “itemN”.
do i = 1 to extent(cArray):
/* do stuff with */ cArray[i]
Group your ASSIGNments
cVar = “abc”.
iVar = 123.
dtVar = now.
ttData.indexField = “Pi”.
ttData.dataField = getPiVal().
assign
cVar = “abc”
iVar = 123
dtVar = now
ttData.indexField = “Pi”
ttData.dataField = getPiVal().
PSC Confidential
Blocks
repeat i = 1 to 10: do i = 1 to 10:
end. end.
if condition1 then if condition1 then

do: assign
cVar = cValue. cVar = cValue
cTime = now. cTime = now.
end.
function, procedure, method all blocks

• Inline code may be faster
– Use includes for code re-use
Error handling
do on error undo, return error ‘oops’:

o = new App.Module.Class().
o:Method1().
o:Method2().
end.
do on error undo, return error ‘oops’:

o = new App.Module.Class().
o:Method1().
o:Method2().
/* Some Other Stuff Happens */
catch e as Progress.Lang.Error:
undo, throw new Progress.Lang.Error (‘oops’).
end catch.
end.
PSC Confidential
Error handling (2)
run method1 in hdl () no-error.

if error-status:error then return error return-value.
run method2 in hdl () no-error.

if error-status:error then return error return-value
run method1 in hdl().

run method2 in hdl().
catch e as Progress.Lang.Error:
undo, throw e.
/* alternatively, throw a new, different error */

undo, throw new Progress.Lang.Error (‘oops’).
end catch.
Class properties
class App.Module.ConferenceVenue:
def public property CityName as char no-undo
get. set.
def public property CityLocation as char no-undo
get ():
/* gets lat/long of city as string
from WebService */
end get.
set.
end class.
o = new App.Module.Object().
Effectively an ASSIGN
o:CityName = “Paris”.
Effectively a
cLoc = o:CityLocation. function invocation
PSC Confidential
Combining techniques
j = extent(cArray).
do i = 1 to j:
cArray[i] = cArray2[i].
end.
j = extent(cArray).
n = 50. /* depends on data distribution */
do i = 1 to j by n:
assign cArray[i] = cArray2[i]
cArray[i+1] = cArray2[i+1]
...
cArray[i+n] = cArray2[i+n].
end.
Loop hoisting
do i = 1 to n: if condition1 then
if condition1 then do i = 1 to n:
do: /* stuff */
/* stuff */ end.
end. else
else if condition2 then
do: /* more stuff */
/* more stuff */ end.
end. else
else do i = 1 to n:
do: /* other stuff */
/* other stuff */ end.
end.
end.
PSC Confidential
Agenda

Testing for performance
Measure performance
• The only way to know for sure
• Measure more than once
• Measure against predefined goals
Use regression test suite
• Use constant, realistic environments
• Compare against baselines
• Automate as far as possible
Ongoing, iterative process
• Engineers’ technical awareness
• User feedback
PSC Confidential
Finding performance problems
Start with code that works

Don’t assume you know what the
problem is
Change one thing at a time
There’s no silver bullet
You will make things worse (probably)
• Take those changes out
The goal posts are always moving
• Stop when it’s good enough
Agenda

PSC Confidential
R-code & PROPATH
Always use r-code in production

• Use –q (Quick Request) parameter
Reduce r-code size
• Remove function prototypes
• Limit use of GLOBAL variables
• Compile with MIN-SIZE option
Keep PROPATH as short as possible
• Order entries by frequency of use
Use procedure libraries
• Memory-mapped when on same machine
In Summary
Good performance needs

upfront work
• Design
• Coding
Measure and test
PSC Confidential
Q&A
Optimization matters only when it matters.

When it matters, it matters a lot, but until
you know that it matters, don't waste a lot
of time doing it. Even if you know it
matters, you need to know where it
matters. Without performance data, you
won't know what to optimize, and you'll
probably optimize the wrong thing.
Joseph M. Newcomer
Optimization: Your Worst Enemy
http://www.codeproject.com/KB/tips/optimizationenemy.aspx
Thank You
PSC Confidential
Additional slides
PSC Confidential
Optimize network roundtrips
loginWindow.w
1 run getLoginLanguages() getLoginLanguages()
2 run getLoginCompanies() getLoginCompanies()
run buildUI().
Optimize network roundtrips
loginWindow.w
run getUIData() getUiData()
1 run getLoginLanguages()
run getLoginCompanies()
run buildUI().
PSC Confidential
Always use NO-UNDO
define variable cVar for char no-undo.
def public property AccessTime as datetime no-undo

get.
set.
define input parameter piParam as int no-undo.
define temp-table ttData no-undo

field indexField as character
field dataField as decimal.
Evaluate functions as rarely as possible
do i = 1 to udfGetNumIter(): j = udfGetNumIter().
end. do i = 1 to j: end.
do i = 1 to num-entries(cLst): j = num-entries(cLst).
end. do i = 1 to j: end.
do i = 1 to 10: j = udfGetMaxValue().
j = udfGetMaxValue(). do i = 1 to 10:
/* do something with j */ /* do something with j */
end. end.
PSC Confidential
Know your indexes
Only maintain the indexes you need

• Add more indexes
• Get rid of unused indexes
Multi-component indexes are good
Unique indexes faster than non-unique
ROWID access is very fast
Efficient data access
Join from smallest bracket to largest Customer
• Not always parent to child

e.g. Date ranges 1
for each Customer where 0..*

credit-limit >= 100,
each Order of Customer where Order
order-date = today:
/* create report */
for each Order where

order-date = today,
first Customer of Order where
credit-limit >= 100:
/* create report */
PSC Confidential
Dealing with LOGICAL and status values
for each Employee where

gender = “Male” and /* or Female */
emp-status = “Perm” and /* or Contract */
currently-employed = true /* or false */
cStatus = “Male” + “|” + “Perm” + “|” + “CurEmp”.

for each Employee where
status contains cStatus:
for each Status where

status = “Perm” or
status = “Male” or
status = “CurEmp”,
each EmpStatus of Status,
each Employee of EmpStatus:
Avoid conditional WHERE clause processing
for each Customer where

(if iCustNum > 0 then cust-num = iCustNum
else true).
define query qryCust for Customer.
if iCustNum > 0 then

open query qryCust
for each Customer where cust-num = iCustNum.
else
open query qryCust for each Customer.
PSC Confidential
CASE faster than nested IF
If cAlpha = “A” then ...

else if cAlpha = “B” then ...
else if cAlpha = “C” then ...
else ...
case cAlpha:
when “A” then ...
when “B” then ...
when “C” then ...
otherwise ...
end case.
For More Information, go to…
PSDN
• Profiler
http://www.psdn.com/library/entry.jspa?externalID=280&categoryID=1801
• LogRead 1.0 Tool Overview (English & Spanish)
http://www.psdn.com/library/entry.jspa?categoryID=62&externalID=1841
• Log Read Utility
http://www.psdn.com/library/entry.jspa?categoryID=41&externalID=349
Documentation:
• OpenEdge® Deployment: Managing ABL Applications
PSC Confidential
Relevant Exchange Sessions
DEV-15: AppServer™ Mode Case

Studies
OPS-23: OpenEdge Performance

Basics
Tools for measuring performance
PROFILER system handle

• Line-by-line execution timings
• Tool available on PSDN
etime
Logging infrastructure
• Useful in production environments
• LogRead utility on PSDN
Wireshark ( http://www.wireshark.org/ )
• Network analyzer
PSC Confidential
[MAYBE] Combining techniques
j = extent(cArray).
do i = 1 to j:
cArray[i] = cArray2[i].
end.
j = extent(cArray).
n = 50. /* depends on data distribution */
do i = 1 to j by n:
assign cArray[i] = cArray2[i]
cArray[i+1] = cArray2[i+1]
...
cArray[i+n] = cArray2[i+n].
end.
[MAYBE] Loop hoisting
do i = 1 to n: if condition1 then
do: /* stuff */
/* stuff */ end.
end. else
else if condition2 then
do: /* more stuff */
/* more stuff */ end.
end. else
else do i = 1 to n:
do: /* other stuff */
/* other stuff */ end.
end.
end.
PSC Confidential

Performance Tips and Tricks With ABL

Uploaded by

Copyright:

Available Formats

Performance Tips and Tricks With ABL

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Performance Tips and Tricks With ABL

Uploaded by

Copyright:

Available Formats

ABL Performance Tips and Tricks

OpenEdge Developer’s Corner

1 © 2009 Progress Software Corporation

Wherefore art thou, performance?

As important as stability, features, quality

2 © 2009 Progress Software Corporation

3 © 2009 Progress Software Corporation

What can I do about it?

Software upgrades vs. hardware

Coding for performance

5 © 2009 Progress Software Corporation

Good design is necessary

6 © 2009 Progress Software Corporation

The fastest code is no code at all

7 © 2009 Progress Software Corporation

Data across the network

Network typically major bottleneck

Network topography has impact …

8 © 2009 Progress Software Corporation

Put your temp-tables on a diet

9 © 2009 Progress Software Corporation

define temp-table ttData ...

run populateData (output table ttData).

define temp-table ttData ...

run populateData (output h).

10 © 2009 Progress Software Corporation

define temp-table ttData ...

run populateData (output table ttData).

define temp-table ttData ...

run populateData (output table ttData by-reference).

11 © 2009 Progress Software Corporation

Understand how indexes work

Understand index selection rules

Confirm actual indexes used

Know your indexes

12 © 2009 Progress Software Corporation

find counters where

13 © 2009 Progress Software Corporation

Unique values (when order doesn’t matter)

14 © 2009 Progress Software Corporation

cDelim = “,”. /* or CHR(3) or | or ... */

15 © 2009 Progress Software Corporation

Group your ASSIGNments

16 © 2009 Progress Software Corporation

repeat i = 1 to 10: do i = 1 to 10:

if condition1 then if condition1 then

function, procedure, method all blocks

17 © 2009 Progress Software Corporation

do on error undo, return error ‘oops’:

do on error undo, return error ‘oops’:

run method1 in hdl () no-error.

run method2 in hdl () no-error.

run method1 in hdl().

/* alternatively, throw a new, different error */

19 © 2009 Progress Software Corporation

20 © 2009 Progress Software Corporation

21 © 2009 Progress Software Corporation

22 © 2009 Progress Software Corporation

Coding for performance

23 © 2009 Progress Software Corporation