Home
Appeon 6.6 Prev Page Prev Page
Appeon Performance Tuning Guide
Appeon Performance
Expected performance level
Automatic performance boosting
Impact of the Internet and slow networks
Impact of “heavy” client-side logic
Impact of large data transmission
Performance-Related Settings
Overview
Appeon Developer performance settings
Appeon Enterprise Manager performance settings
Timeout settings
DataWindow data caching
Multi-thread download settings
Custom Libraries download settings
Log file settings
Internet Explorer performance settings
Web and application server performance settings
SAP Sybase EAServer
JVM startup option
Configuring data sources
HTTP properties
Microsoft IIS server
Recommendations for avoiding common errors on IIS
Advanced thread settings
Database performance settings
Recommended database driver
Recommended database setting
Identifying Performance Bottlenecks
Overview
Heavy window report
Appeon Performance Analyzer
Getting Started
Enabling Appeon Performance Analyzer
Starting Appeon Performance Analyzer
Getting to know Appeon Performance Analyzer
Removing Appeon Performance Analyzer
Working with Appeon Performance Analyzer
System Configuration
Calls Analysis
Download Analysis
View Detail
Additional Functions
Testing Appeon Web applications with LoadRunner
LoadRunner
General Limitations on Performance Testing
Testing Environment
Testing Steps
Configuring AEM
Data Preparation (for update only)
Preparing Test Cases
Recording Scripts
Modifying Scripts
Additional steps for Update operation
Parameterization of SQL statements
Playing back Script to test the correctness of scripts
Setting Scenarios
Additional steps for Update operation
Running Scenarios
Appendix
Modifying the scripts of NVO
Modifying the scripts of EJB/JavaBean
Troubleshooting
Errors appear when playing back scripts with LoadRunner 8.0
The value of sessionID is null
Error message appears in script playback
Error message in Appeon Log
Failed to parameterize scripts
Out of memory error and application server shut down
Field values do not change after parameterization and playback
Runtime errors causing scenario failure
Transactions failed
Unable to connect to remote servers
Analyzing log files
Analyzing Windows application log files
Analyzing Appeon Server log files
Analyzing active transaction log
Identifying Performance Bottlenecks of Web Server and Application Server
Identifying Performance Bottlenecks of DB Server
Deadlock analysis
Identifying Performance Bottlenecks of PB application
Analyzing performance bottlenecks of PB application
Tuning: DB Server
Database
Tuning: Excessive Server Calls
Overview
Technique #1: partitioning transactions via stored procedures
Technique #2: partitioning non-visual logic via NVOs
Technique #3: eliminating recursive Embedded SQL
Technique #4: grouping multiple server calls with Appeon Labels
Tuning: Heavy Client
Overview
Technique #1: thin-out “heavy” Windows
Technique #2: thin-out “heavy” UI logic
Manipulating the UI in loops
Triggering events repeatedly
Performing single repetitive tasks
Initializing “heavy” tabs
Using ShareData or RowsCopy/RowsMove for data synchronization
Using computed fields
Using DataWindow expressions
Using complex filters
Using RowsFocusChanging/RowsFocusChanged events
Technique #3: offload “heavy” non-visual logic
Tuning: Large Data Transmissions
Overview
Technique #1: retrieving data incrementally
For Oracle database server
For all other database servers
Technique #2: minimizing excessive number of columns
Conclusion

System Configuration

In order to make Appeon Performance Analyzer more convenient for future use, you can make some configurations in the System menu.

Click menu System | Config. The Appeon Performance Analyzer Configuration dialog opens:

Appeon Performance Analyzer Configuration dialog

Enable Tracing

This option controls if Appeon Performance Analyzer works or not. If you want to work with Appeon Performance Analyzer to analyze an application program, the option must be selected. By default it is selected.

Instant update

By selecting Instant update, the analyzing data in the analyzing panel can be updated instantly when operation changes. When Instant update is not selected, Performance Analyzer will work faster; but users will need to manually click menu View | Update to see the latest data.

Restore to default location

By selecting this option, the main window of Appeon Performance Analyzer always opens at the default position. By unselecting this option, Appeon Performance Analyzer will remember its last position on the screen when it exits, and will open at the last location on the screen when it starts next time. By default, this option is selected.

Show window when started

By selecting this option, Appeon Performance Analyzer will automatically start when the Web application runs. You can deselect this option to disable the automatic starting of Appeon Performance Analyzer, and manually Start Appeon Performance Analyzer by pressing Ctrl + Shift + F12. By default it is selected.

Enable log file

If you want to save the analyzing log in the local machine, select Enable log file. And the log file will be created after the Web application is closed.

Enable log file option

As shown above, the default destination is in C:\ disk. You can specify a different location by clicking Browse to select an existing folder on your computer.

Clear previous log files when tracer started

This option becomes selectable when Enable log file is selected. If you want to clear the analyzing log files saved in the last starting of Appeon Performance Analyzer, select this option.

After you finish the configuration, click OK to close the dialog.