Loading issue very slow

[Yahia TERZI]

Dears,

We are about deploying Jira 6.1 and we meet some issue performance for viewing an issue on browser, FireFox Chrome Latest versions.

it took around 20 sec to get response from a jira server where the client machine and Jira are in the same segment of Lan .

We make the tricks below :

http://blogs.onresolve.com/2009/04/how-to-make-jira-twelve-times-faster/

http://blogs.onresolve.com/2009/04/how-to-make-jira-6-12-times-faster/

and resizing the JVM Ram allocation with no significatif results.

Where can be a problem ?

Regards

[eClerx Orion]

Hello,

We are using jira 6.3.9.

When we are trying to edit issue , EditIssue!default.jspa?id=131682 this URL hit from jira end and it will take more than 25 seconds on production server.

Same issue when we are editing on stage and QA envireonment it will take 12-15 seconds to load.

• QA -  Total issue (52000)
• STAGE -  Total issue (55000)
• PRODUCTION -  Total issue (94000)

So why it is taking more time to load edit issue page on production server.

[Yahia TERZI]

Hi all,

at end, the issue isn't in jira but in a CF that uses a DB view.

we optimized the view and the time to load an issue in browser passes from 20 seconds to 1/2 second.

thnx for all.

Regards,

Yahia

[Alex Shchagin]

Please descrive your environemnt in details: what database, hardware, JVM settings do you use

[Radu Dumitriu]

There can be multiple causes: database responding slowly, Custom Fields which are slow to load, etc

Does JIRA respond the same way from the local machine (i.e. server)? If no, there's a networking problem (assuming the database is on the same machine). How did you configure it ? What means "resizing the JVM Ram" ?

You need to profile it to see where it is spending time.

There's not enough information on this for anybody to tell you what's going on there.

[Yahia TERZI]

Hi Radu,

Always so fast to response.

Yes, Jira responses with same way in local or remote machines.

APP server and DB are in same machines.

We increase JVM heap size.

We have not yet profiling due to time contraint. one we do it, w'll update the question.

warm regards

[Yahia TERZI]

Below some details for the environnement:

OS : 2K8 R2 Std
CPU : Intel Quad Core 2.4 Ghz & 8 G Ram

JVM : 1.7
Heap size : 1 Go, Max and Min are equals

DB : SQL SERVER 2008

Jira 6.1

[Radu Dumitriu]

1Gb is probably low.

[Yahia TERZI]

i will increase tommorow to 2GB.

Radu, i made a quick profiling and i got IssueNavAction.execute() takes 30 sec to finish.

[Alex Shchagin]

Copy and paste profiling data for a single request here or attach a piece of log