Troubleshooting
Problem
Initial LQE or LDX indexing can be slower than expected (~1 million resources per day) when installed on virtualized Microsoft Windows server environments.
Symptom
Testing shows that LQE/LDX indexing can run at the rate of ~1 million resources per day when you run on ideal hardware as described in Best Practices for Configuring LQE for Performance and Scalability.
It has been observed in some cases that initial indexing is much slower.
Cause
The root cause of the issue is the same as in the technote 6450347: IBM Engineering Lifecycle Query Engine performance is very poor for query and indexing on Windows servers. Refer to that technote to find the root cause.
Diagnosing The Problem
Use the diagnostics provided in the technote 6450347: IBM Engineering Lifecycle Query Engine performance is very poor for query and indexing on Windows servers.
Resolving The Problem
A JVM argument is available in LQE 6.0.3 iFix006 and 6.0.4 through Add a hook to force Jena to direct mode (418787) to switch Jena to use Direct-access mode that avoids use of the method found to be the bottleneck.
For Tomcat or WebSphere Liberty, the argument can be applied by adding the following line in the JVM arguments section in the startup script.
To set the JVM parameter on WebSphere Application Server, refer to technote 397841: Setting generic JVM arguments in WebSphere Application Server
Note: The server must be restarted after making the change in order for the change to take effect.
Once the initial LQE indexing has completed, remove the property and restart the server when possible.
While enabling this argument should increase the throughput of the initial indexing, it is highly recommended to switch back to memory mapped mode once the initial indexing has completed in order to take advantage of faster query performance.
To enable direct-access mode for Jena, add the JVM argument -Dlqe.jena.direct.mode to the server and set its value to true
For Tomcat or WebSphere Liberty, the argument can be applied by adding the following line in the JVM arguments section in the startup script.
set JAVA_OPTS=%JAVA_OPTS% -Dlqe.jena.direct.mode=true
To set the JVM parameter on WebSphere Application Server, refer to technote 397841: Setting generic JVM arguments in WebSphere Application Server
Note: The server must be restarted after making the change in order for the change to take effect.
Once the initial LQE indexing has completed, remove the property and restart the server when possible.
[{"Type":"SW","Line of Business":{"code":"LOB59","label":"Sustainability Software"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSTU9C","label":"Jazz Reporting Service"},"ARM Category":[{"code":"a8m0z000000GmlzAAC","label":"Jazz Reporting Service->Lifecycle Query Engine->Performance \/ MBeans"}],"ARM Case Number":"","Platform":[{"code":"PF033","label":"Windows"}],"Version":"All Version(s)"}]
Was this topic helpful?
Document Information
Modified date:
28 May 2021
UID
swg22007476