It can take anywhere from 10 to 30 seconds to render any system admin pages. This is not a new development. I suspect a poor configuration somewhere. Rather than me flailing around, I would very much appreciate guidance on where to look first.
We're running JIRA v6.2.4 on Centos. Connected to a remote Postgresql database.
There's a few things to check:
1) When this behavior started? After an upgrade or any network change?
2) Does it help increasing the memory available for the JVM (Both JVM_MINIMUM_MEMORY and JVM_MAXIMUM_MEMORY)?
3) Does the same problem occurs when bypassing the proxy? (Acessing Jira locally, as localhost:port)
1) It's been slow since I've been here.
2) I see no OutOfMemory errors in the logs. I would wouldn't I?
3) Yes. Proxy does not appear to be the problem.
I'm attaching a splunk output from a test I did. I turned up a bunch of the logging. First datetime below is immediately after I selected "Workflows". Second datetime is immediately after it rendered.
[root@atlassian-jira log]# date --rfc-3339='ns' 2014-05-13 16:04:34.928704410+00:00 [root@atlassian-jira log]# date --rfc-3339='ns' 2014-05-13 16:05:04.635459081+00:00
In the spreadsheet you'll see big gaps in the log entries. Between row 175 and 180, almost 16 seconds elapses. What's it doing?
Between rows 410 and 411, 4 seconds elapse.
Almost 3 seconds between 535 and 536.
In total, it took about 29 seconds before the screen rendered. Which I hope you would agree is terrible.
All guidance appreciated.
Supported Platforms macOS Windows We recently introduced support for additional hosting services such as GitHub Enterprise, GitLab (Cloud, Community Edition, Enterprise Edition), and...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs