Just for information for the general population, the backend database in Rally does keep a number of indexes on fields to speed up fetches. This is more relevant when you have the records sorted on those fields as well.
Custom fields may not have those indexes. When you get an answer from support, I would be interested to hear it.
------------------------------
Nik
Rally Sales Engineer
Rally Software
------------------------------
Original Message:
Sent: 01-17-2020 09:50 AM
From: Pat Cousins
Subject: Performance issues when using custom fields?
Thanks for checking, Mitch. It only seems to affect certain custom fields. I am working with Rally Support on this.
Original Message:
Sent: 01-16-2020 04:04 PM
From: Mitch Goldman
Subject: Performance issues when using custom fields?
Just played with the concept on portfolio items and didn't notice an impact due to custom fields.
Tried it again at the user story level across the entire workspace and see a slight difference, but I don't know I would have noticed if I wasn't timing it. But you may have many more items stored than I do, so it could be a difference in scale.
Original Message:
Sent: 01-16-2020 03:04 PM
From: Pat Cousins
Subject: Performance issues when using custom fields?
I'm curious if other subscriptions are seeing a performance issue in Rally when querying or filtering on custom fields? As an example, the Portfolio Items page takes a few seconds to load when filtered on core fields, but about 45 seconds when filtered on a custom field.