[#CWD-772] Crowd client libraries and caching need further review to improve JIRA performance

Crowd

Crowd client libraries and caching need further review to improve JIRA performance

Created: 30/Jan/08 05:54 PM Updated: Tuesday 07:23 PM

Component/s:

Performance

Affects Version/s:

None

Fix Version/s:

1.6

Time Tracking:

Original Estimate:

Not Specified

Remaining Estimate:

0 minutes

Time Spent:

4 hours

Issue Links:

Part

This issue incorporates:

~~CWD-1058~~ Improve JIRA integration by consolidating the findAllPrincipalNames() call with the individual calls to retrieve users.

Reference

This issue is related to:

CWD-763 Crowd client libraries for JIRA using AD with SSL enabled are unacceptably slow.

CWD-536 JIRA performance improvements

~~CWD-614~~ Implement caching on Crowd client layer

Participants:	David O'Flynn [Atlassian], Donna McGahan [Atlassian] and Eric Anderson
Since last comment:	4 weeks, 1 day ago
Support reference count:	9
Labels:

Description

« Hide

Due to JIRA's use of OSUser framework for user management, all users, groups and memberships are requested during common actions like Add Project. If Crowd integration is using a large directory, this can cause serious degradation in JIRA performance. The Crowd client libraries may not be caching this data effectively to help rectify this problem.

All

Comments

Work Log

Change History

Sort Order:

[ Permlink | « Hide ]

David O'Flynn [Atlassian] added a comment - 03/Jun/08 01:40 AM - edited

Some test results that may be of interest.

Setup

JIRA & Crowd on one machine.
Internal directory with 1 user in PostgreSQL on same machine.
Active Directory 2003 in a VM on a different machine. This is a slow server.
Just over 2000 users in AD instance.
SSL not enabled.

Reloading the User Cache

Before: 55-60 seconds.
After: 2-3 seconds.

Your results will vary depending on your configuration, the size of your directory instance, and on how fast it is.

[ Permlink | « Hide ]

Eric Anderson added a comment - 07/Aug/08 09:40 PM

When are we going to see a fix for this if its not done yet?

And will we see another 1.4 point release for this or am I going to have to risk even more new features on our production systems in order to get the bug fixes?

[ Permlink | « Hide ]

Donna McGahan [Atlassian] added a comment - 07/Aug/08 10:59 PM

Hi Eric,

I have re-opened this because, JIRA's cache will expire on a periodic basis which may cause serious performance hits until the cache has been rebuilt. I think we still have some investigation to do with regard to smarter cache updating. Unfortunately, I cannot provide an estimated fix version for this at this time. I'm hoping to discuss this with the dev team next week to see where we can fit this in the road map or, perhaps, if I should raise a new, more specific issue for this.

I know you experienced some issues with JIRA integration and Crowd's nested-groups capability in the 1.4 release, which we were able to resolve. I completely understand your hesitancy to upgrade to a new major release as a result of this. Please know the team is working hard to provide a smooth 1.5 release.

Cheers,
Donna