Details
-
Type:
Bug
-
Status: RESOLVED
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 19.7 [Tentative], 20.3 [Tentative], 21.0 [Tentative], 22.0 [Tentative]
-
Fix Version/s: 22.0 [Tentative]
-
Component/s: Config
-
Labels:
-
Test Plan:
Description
While doing some work lately I found this useful property for hibernate performance tuning and checked that it was already enabled and not possible to disable.
In KNL-1583 a setting was added to the hibernate properties for generate_statistics.
Every article I've read
https://thorben-janssen.com/how-to-activate-hibernate-statistics-to-analyze-performance-issues/
https://www.baeldung.com/hibernate-common-performance-problems-in-logs
indicates that having this true in production can lead to decreased performance. However it can be useful in development to uncover N+1 style issues. I think we should make this configurable and also document better how to use this property. I was seeing some potential N+1 issues in assignment yesterday as it looked to be doing an inefficient query when pulling down submissions.
I don't know the performance impact of having this on but there's no point if it's not even logged by default.
Gliffy Diagrams
Zeplin
Attachments
Issue Links
- relates to
-
SAK-39387 Move Hibernate SessionFactory to JPA EntityManager
-
- RESOLVED
-