Documentation for JIRA 4.0. Documentation for other versions of JIRA is available too.

We have a utility that you can run to get disk access times. Use it if JIRA or Confluence is running slowly and you suspect that disk access speed is the culprit (or you want to rule it out).

Run it from the machine that JIRA or Confluence is running on, from the directory you have downloaded support-tools.jar to.

java -Djava.io.tmpdir=<index directory> -jar support-tools.jar

For JIRA 4.x the index directory is <jira_home>/caches/indexes

This should give you a result like:

Good

Linux Workstation A

My local machine, which is not slow:

TOTALS
----    ----    ----    ----    ----
stat    avg     median  min     max
----    ----    ----    ----    ----
open    75,830  62,000  44,000  2,869,000
r/w     46,407  40,000  35,000  907,000
close   5,751   5,000   4,000   336,000
delete  118,942 81,000  65,000  22,864,000
----    ----    ----    ----    ----
All times are in nanoseconds.

Linux Workstation B

TOTALS
----    ----    ----    ----    ----
stat    avg median  min max
----    ----    ----    ----    ----
open    32,254  29,916  18,610  692,447
r/w 23,676  20,309  17,888  411,218
close   4,857   4,374   3,617   221,829
delete  36,232  34,753  22,000  425,200
----    ----    ----    ----    ----
All times are in nanoseconds.

Bad

TOTALS
----    ----    ----    ----    ----
stat    avg     median  min     max
----    ----    ----    ----    ----
open    275,886 267,184 246,412 2,544,101
r/w     92,956  81,538  70,727  7,358,896
close   3,194,958       3,177,771       3,076,064       4,331,872
delete  542,650 530,271 514,226 1,771,416
----    ----    ----    ----    ----
All times are in nanoseconds.

This site had REALLY fast disks but with a virus scanner turned on!

平均

An ordinary Mac Mini's local SATA disk with a Journaled HFS+ file system. Don't forget to run the test a few times to avoid outlying results - delete maximums seems to be especially slow on the first run.

TOTALS
----	----	----	----	----
stat	avg	median	min	max
----	----	----	----	----
open	134,208	133,000	79,000	575,000
r/w	57,026	52,000	31,000	747,000
close	95,598	91,000	55,000	440,000
delete	293,109	275,000	82,000	9,371,000
----	----	----	----	----
All times are in nanoseconds.

Why would disk access be slow?

Some things that can cause slow disk access are:

  1. virus checkers
  2. remote disks or shared drives
  3. synchronization to other machines over a slow network

VMWare

Because we get asked how JIRA performs when running in a VMWare image, here are some results for VMWare. These images were both running on Testing Disk Access Speed.

Windows in VMWare

TOTALS
----	----	----	----	----
stat	avg	median	min	max
----	----	----	----	----
open	593,183	548,114	426,591	8,659,481
r/w	173,372	159,517	10,895	1,954,718
close	174,506	141,079	29,333	17,045,183
delete	405,493	372,673	14,248	7,665,499
----	----	----	----	----
All times are in nanoseconds.

Linux in VMWare

TOTALS
----    ----    ----    ----    ----
stat    avg     median  min     max
----    ----    ----    ----    ----
open    84,324  46,000  35,000  16,700,000
r/w     124,550 50,000  41,000  61,272,000
close   17,936  16,000  14,000  961,000
delete  64,528  49,000  36,000  3,603,000
----    ----    ----    ----    ----
All times are in nanoseconds.

This shows that, at least in our testing, you should not run JIRA in VMWare, as disk access, is much slower than on a native operating system installation.

参考情報