Using Warmup to Improve Transaction Performance
- Josef Mayrhofer
- 14 hours ago
- 2 min read
This guide explains the configuration needed for Warmup and provides details about the supported applications.
Why Warmup Exists
When the first transaction in a session is executed, it usually takes longer than subsequent ones. This delay occurs because the system needs to load static or configuration records from disk into the cache during that first transaction.
The Warmup feature accelerates this process by preloading those configurations and static records into the cache before the user initiates a transaction. This significantly reduces transaction execution time.
Working with Warmup Applications
This application stores the list of applications and their record IDs in an associated multi-valued set.
Here you define:
Which applications must be preloaded
Which record IDs for those applications should be cached
The Application field is a multi-value set, and Record ID is a sub-value set for each application.
Tip:
You can use an asterisk (*) in the Record ID field to cache all records of an application.
Caching LOCAL.TABLE
To cache LOCAL.TABLE, you must:
Define the keyword CACHE.LOCAL.TABLE in the Application field
Configure the list of record keys in the Record ID field
Enter the common API EB.PRE.LOAD.DATA in the Read Api field
Caching EB.LOOKUP
To cache EB.LOOKUP, you must:
Define CACHE.EB.LOOKUP in the Application field
Configure the list of record keys in the Record Id field
Enter EB.PRE.LOAD.DATA in the Read Api field
Caching Classes
If, instead of records, you need to preload a set of classes, you can use the keyword CACHE.CLASSES.
This option has specific checks and validations, described below.
To cache classes:
Enter the class names in the Read Api Info field
Leave the Record Id field blank
Enter EB.PRE.LOAD.DATA in the Read Api field
EB.WARMUP.SESSIONS
This application is the starting point of the Warmup framework in Transact.
The framework searches for a matching definition based on the Channel Name (OFS.SOURCE).
EB.WARMUP.SESSIONS allows you to associate multiple EB.WARMUP.GROUP records, which the Warmup process refers to in order to determine what content should be cached.
The @ID of this application corresponds to the OFS.SOURCE for which the records are cached per session.
There are many other components within the T24 core banking system where Warmup can be applied, including APIs and server-side data.
At Performetriks, we prioritize information security just as much as the performance of your banking systems. If you need assistance analyzing where you should apply Warmup and how to implement it, feel free to contact us. At Performetriks, it will be our pleasure to assist you.
Happy Performance Engineering!
Comments