TAP – R23 Precomp Performance
October 2024
Felipe Barahona
Information in this document is subject
to change without notice.
No part of this document may be
reproduced or transmitted in any form or
by any means, for any purpose, without
the express written permission of
TEMENOS HEADQUARTERS SA.
© 2022 Temenos Headquarters SA -
all rights reserved.
LNVL – TAP R23 Precomp Preformance Guide
Introduction
Precomp is a daily process that runs in the OCS Server and mostly with DB CPU effort to
calculate.
Run precomp
Precomp process is executed from OCS server with ocs user.
The precomp can be done in FULL mode or entity-list specific.
The shell script precomp-entity.otf-shell is the core product, but depending on the list definition
it is highly probable to modify or create a new one.
Full precomp
Depending on the volume, the full process take minutes or hours, it is recommended to be run
from inside a server.
We suggest to run the shell with an output file to monitor and review the console output.
Consider to review the WUI result also for a deeper analysis.
./otf-shell.sh -f otf-shell/precomp-entity[CUSTO].otf-shell > precomp-entity[CUSTO].otf-shell.out
Specific precomp
Connect and navigate to the path:
/wealthsuite/ocs/current/admin
Launch the OTF Shell
./otf-shell.sh
2 Temenos
LNVL – TAP R23 Precomp Preformance Guide
login
advisor
[password]
** If password is not working, please update and reinstall of OCS with new password is needed
to be applied
Successful login
From the script precomp-entity[CUSTO].otf-shell choose the desired line. For example:
submit-bpi-job -D entity=instrument -D entityDimE=2 -D entityDimCode=LV_INSTR_0_25K
-D chunkSize=700 -t 7200 -w tsl-precomp-entity-job.xml
Example of a successful result
Monitoring
If a job is launched with a small timeout, it can be monitored from the background with the
command:
3 Temenos
LNVL – TAP R23 Precomp Preformance Guide
monitor-job -i [Job Id]
Additionally the job can be monitored through WUI console. Go to Admin and check the running
instance.
Performance Tunning
The precomp can turn complex to tune when there is huge amount of data to calculate.
Please note that as core product is released it will have default values for processing threads
and number of DB connections.
These variables can be modified to improve the precomp times. Although when you increase the
values there will be additional workload in DB Server.
The number of threads is configured in the file oetf-joblauncher-config.xml. This file is not
available by default and each time the OCS is reinstalled it will be deleted.
To build the oetf-joblauncher-config.xml file, please follow these steps:
- OCS must be up and running.
- Connect to otf-shell.sh and login.
- Run “config”
- The oetf-joblauncher-config.xml fill will be created in the path
wealthsuite/ocs/current/temp/ocs-config-files
- Copy the file to /wealthsuite/ocs/current/webDomain/config
- Modify the values as needed. The suggested values have a 4x1 ratio and must be
analyzed after each run. If you increase the values too much, then you will run out of DB
connections and also the TAP DB memory and cpu will reach stress levels. We will give
more details of this step below.
- Stop and Start OCS for changes to take effect after each change.
DB connections
During the performance tuning, it is highly probable that you run out of DB connections. Note
when there are multiple threads additional DB connections will be needed.
- Modify the all-in-one.dpi.properties and add the below values. Reinstall OCS.
###############################################################
# tslDB
#
jdbc.tsl.min.connections = 0
jdbc.tsl.max.connections = 2500
Precomp multi thread tune
Now we will go back to the oetf-joblauncher-config.xml. To start the performance testing you
need to update only the parameters
- TSL precomp entity job
o joblauncher:chunk
max-threads
max-threads-per-job-instance
- Don´t update other values.
- Maintain the 4x1 ratio.
4 Temenos
LNVL – TAP R23 Precomp Preformance Guide
Each time you update the values run again a precomp command. Run for a specific entity which
is generating long times.
Monitor DB Server CPU and Memory. Probably additional resources will be needed in the DB
server to improve the performance, but this can be a conclusion only when the precomp times
improve and the next bottleneck is the DB server.
Chunk Size
Finally, tune the “chunkSize” increasing and decreasing the value. This value has to be modified
and tested in independent iterations. This will help reach the best value for each entity.
submit-bpi-job -D entity=instrument -D entityDimE=2 -D entityDimCode=LV_INSTR_0_25K
-D chunkSize=700 -t 7200 -w tsl-precomp-entity-job.xml
5 Temenos
