Uploaded image for project: 'Jira Platform Cloud'
  1. Jira Platform Cloud
  2. JRACLOUD-66614

Searchable Fields Slow - Get a sorted list of searchable fields is more than 160 times slower

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Low Low
    • None

      Get a sorted list of searchable fields is more than 160 times slower in JIRA 6 than in JIRA 5.2. This comes from the fact that translatable field names was introduced in JIRA 6 which means that JIRA has to get a property set for each field where the translated name is stored for that field when it get the field's name now.

      These property sets should be cached but it looks like if there is a high number of fields most of the caches are empty and have to be looked up from the DB from scratch which is taking all the time.

      We need to introduce a more performant field name cache in JIRA.

      Workaround
      Upgrade to JIRA 6.0.1

          Form Name

            [JRACLOUD-66614] Searchable Fields Slow - Get a sorted list of searchable fields is more than 160 times slower

            crf added a comment - - edited

            There were two problems involved:

            1. The custom field translation lookup was supposed to be cached, but the cache wasn't working (the new problem introduced by the translations), which increased the time needed to resolve the name of a custom field.
            2. The report configuration page had a problem that caused the sorted set to be recalculated once per field instead of reusing a single sorted set. This was an existing problem.

            On the report configuration page, these two problems combined to make that page particularly slow. Both of them are addressed in 6.0.1/OD-15.

            crf added a comment - - edited There were two problems involved: 1. The custom field translation lookup was supposed to be cached, but the cache wasn't working (the new problem introduced by the translations), which increased the time needed to resolve the name of a custom field. 2. The report configuration page had a problem that caused the sorted set to be recalculated once per field instead of reusing a single sorted set. This was an existing problem. On the report configuration page, these two problems combined to make that page particularly slow. Both of them are addressed in 6.0.1/OD-15.

              edalgliesh Eric Dalgliesh
              mandreacchio Michael Andreacchio
              Affected customers:
              1 This affects my team
              Watchers:
              6 Start watching this issue

                Created:
                Updated:
                Resolved: