Using localtime in application code to conduct performance timing tests resulted in unexpected CPU spikes and bad timing results
(Doc ID 1923450.1)
Last updated on APRIL 14, 2022
Applies to:
Oracle TimesTen In-Memory Database - Version 11.2.1 and laterInformation in this document applies to any platform.
Symptoms
User was attempting to measure timings for a large load of Oracle and TimesTen queries. User noticed that lots of their testing results showed high CPU times and unexpected longer timings compared to performance timing tests conducted directly against Oracle and Timesten (i.e. measurements wasn't done by their application). This pointed toward an issue within their application code or integration.
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
Symptoms |
Cause |
Solution |