Loading...

XML

Word

Printable

Feedback Policy:

We collect Jira feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

NOTE: This suggestion is for JIRA Server. Using JIRA Cloud? See the corresponding suggestion.

When bottlenecks are identified - raise JAC issues and link back to this Epic

incorporates

JRASERVER-27206 The upgrade to using Lucene 3.0 has caused performance degradation where there are large result sets sorted by date

JRASERVER-22157 JIRA Performance degrades significantly for a short time after editing any custom field if you have a lot of custom fields

JRASERVER-27402 SearchProvider.searchCount uses a TopDocCollector

JRASERVER-27421 Standalone does not have sensible defaults for the connection pool

JRASERVER-27422 InstrumentationConfiguration.isCPUPostCollected calls IsDevMode a lot -this is a blocking call

JRASERVER-27308 The IssuesFragment panel has a poor performance profile

JRASERVER-27538 The Issues Search performs poorly when sorting by a User field

relates to

JRACLOUD-27880 Analyse JIRA performances and Identify bottlenecks

(2 incorporates, 1 relates to, 1 mentioned in)