Using profiling mechanism
The Product Master profiling mechanism provides information about bottlenecks, especially when investigating performance problems due to custom implementations (any scripted implementations).
You need to enable profiling by setting the profiling_info_collection_depth
parameter in the common.properties file to a sufficiently high number (for
example, 50). To profile scheduled jobs, the profiling_scheduled_jobs parameter
in the common.properties must be set to
full. Note: delete all of the former profiling information as otherwise retrieval of
profiling information might be slow and lots of database disk space is consumed.
To access the collected performance information in the Product Master user interface, click System Administrator > Performance Info > … menu
Profiling
To access profiling in the Product Master user
interface, click System Administrator > Performance Info > Profiling.
Profiling displays which function calls the most time is spent. Profiling information is accessed
either through:
- System Administrator > Performance Info > Profiling, or
- in case of scheduled jobs, click View Details while you are on the Schedule Status Information and then click Performance data.
Database performance
To access profiling in the Product Master user interface for the database performance, click System Administrator > Performance Info > DataBase Performance.
The database performance view provides a statistical overview for each static query also for queries that are associated with each page. Analyzing the db.log file with the sumall.awk script is more straight forward and dynamic queries can be differentiated.
Click a specific query displays the query automatically in the DB Admin
window and up to three argument sets can be retrieved.
Note: Dynamic queries are not
tracked.