• Icon: Suggestion Suggestion
    • Resolution: Fixed
    • 2.1
    • Caching
    • None
    • 3
    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      Populate Crowd with 50,000 users and integrate JIRA — then report back on problems and come up with solutions!

            [CWD-536] JIRA performance improvements

            With Crowd 2.1 and JIRA 4.3, we've re-architected the way that sync works, so that app performance is not affected while the sync is underway.

            David O'Flynn [Atlassian] added a comment - With Crowd 2.1 and JIRA 4.3, we've re-architected the way that sync works, so that app performance is not affected while the sync is underway.

            CWD-772 contains updates on significant JIRA performance improvements coming in 1.4.3

            David O'Flynn [Atlassian] added a comment - CWD-772 contains updates on significant JIRA performance improvements coming in 1.4.3

            We only have 100 or so users and our instance is dreadfully slow as well

            Eric Anderson added a comment - We only have 100 or so users and our instance is dreadfully slow as well

            We have 7000+ users in Crowd and there are a couple of places that could use some speedups.

            Currently, when JIRA needs Crowd information, it can be a painfully slow process if Crowd is refreshing its cache.

            One suggestion would be to limit the users that JIRA's User Picker requests from Crowd to only those users in groups authorised to log in to JIRA (eg: jira-users). (Would you want to assign an issue to someone who isn't able to use the system?)

            I'll comment more as we come across situations during usage.

            Graham Bakay added a comment - We have 7000+ users in Crowd and there are a couple of places that could use some speedups. Currently, when JIRA needs Crowd information, it can be a painfully slow process if Crowd is refreshing its cache. One suggestion would be to limit the users that JIRA's User Picker requests from Crowd to only those users in groups authorised to log in to JIRA (eg: jira-users). (Would you want to assign an issue to someone who isn't able to use the system?) I'll comment more as we come across situations during usage.

              shamid@atlassian.com shihab
              justen.stepka@atlassian.com Justen Stepka [Atlassian]
              Votes:
              8 Vote for this issue
              Watchers:
              10 Start watching this issue

                Created:
                Updated:
                Resolved:

                  Estimated:
                  Original Estimate - Not Specified
                  Not Specified
                  Remaining:
                  Remaining Estimate - 0h
                  0h
                  Logged:
                  Time Spent - 8h
                  8h