[#JRA-5263] Cache size > cache capacity?

JIRA

Cache size > cache capacity?

Created: 18/Nov/04 03:56 AM Updated: 08/Oct/08 01:53 AM

Component/s:

Backend / Domain Model, Performance

Affects Version/s:

3.0

Fix Version/s:

None

Time Tracking:

Not Specified

Environment:

SUN 1.4.2_04 on RH EL3 (server vm, parallel gc)

Participants:	Ingomar Otter [Valtech] and Jeff Turner [Atlassian]
Since last comment:	4 years, 2 weeks, 2 days ago
Labels:

Description

« Hide

General observation: Since the 3.0 upgrade, JIRA consumes a lot of memory. It is therefore sometimes pretty slow.

I order to reduce memory usage, I ve decreased the issue cache capacity. It is now set to 500.
However I've just looked into the stats and it shows a "current cache size" of 2102. How can this happen?
Can JIRA effectivly work with cach sizes < max result set sizes?

All

Comments

Work Log

Change History

Sort Order:

[ Permlink | « Hide ]

Jeff Turner [Atlassian] added a comment - 19/Nov/04 12:06 AM

Hi,

How do you relate memory consumption to slowness? Are you getting
OutOfMemoryErrors in the logs? Unless you have allocated more memory
than you have physical memory, and JIRA is swapping onto disk, I don't
think memory use would affect performance at all.

There are a number of issues affecting performance listed at:

http://www.atlassian.com/software/jira/docs/latest/performance.html

As to your question: did you flush the cache stats after resizing? JIRA
will run quite a bit slower if not all issues are cached, as they all
have to be loaded whenever a full-issue search is done (to sort the
issues).

Cheers,

--Jeff

–
ATLASSIAN - http://www.atlassian.com
Expert J2EE Software, Services and Support
jira-support@atlassian.com ICQ: 326266423
JIRA Docs: http://www.atlassian.com/software/jira/docs/latest