Details
-
Suggestion
-
Resolution: Duplicate
-
None
-
None
-
17
-
19
-
Description
NOTE: This suggestion is for JIRA Server. Using JIRA Cloud? See the corresponding suggestion.
I am creating this issue as per the feedback from one of our customers.
He reported that after his DBA reviewed their AWR reports, they noticed that a query to the PROPERTYENTRY table (copied below) was among the top queries by elapsed time and CPU time, gets and executions.
SELECT ID, ENTITY_NAME, ENTITY_ID, PROPERTY_KEY, propertytype FROM propertyentry WHERE ENTITY_NAME=:1 AND ENTITY_ID=:2 AND PROPERTY_KEY=:3
After modifying an existing index for this table , they saw an improvement of 35 times in the access speed and CPU usage.
This might be Oracle-specific, but I think we should review whether this index should not be modified during the JIRA installation.
Attachments
Issue Links
- duplicates
-
- Closed
- is related to
-
- Closed
-
- Gathering Interest
-
JDEV-29434 Loading...
- relates to
-
JRASERVER-64928 Slow performance due to high number of rows in the entity_property table
-
- Closed
-
-
- Closed