[OPENAM-6545] ServerInfoResource should attempt to cache ServiceConfigs per realm rather than creating one on each request Created: 06/Aug/15 Updated: 20/Nov/16 Resolved: 13/Aug/15
|Affects Version/s:||12.0.0, 12.0.1, 13.0.0|
|Fix Version/s:||12.0.2, 12.0.3, 13.0.0|
|Reporter:||Mark de Reeper||Assignee:||Mark de Reeper|
|Sprint:||Sustaining Sprint 10|
|Support Ticket IDs:|
During the investigation of a performance issue it was observed that ServerInfoResource.getServiceConfig() was constructing a ServiceConfigManager on each invocation which under heavy loads can lead to blocked threads in ServiceConfigImpl
Caching the ServerConfig per realm is one approach to solving the problem.
|Comment by Mark de Reeper [ 13/Aug/15 ]|
Fixed in r15114 and r15115.
|Comment by Nemanja Lukic [ 29/Sep/15 ]|
Verified in: OpenAM 12.0.2 Build 15797 (2015-September-21 17:41)
|Comment by Richard Hruza [ 05/May/16 ]|
I executed a jmeter HTTP requests:
These requests were executed in 4 threads for 5000 loops = 40 000 requests. 40000 requests were done in 27.3s .I did not observe error in the debug log. See also