You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm not sure if this is down to the configuration of the repository, or if it's a problem on the Redmine side of the equation ; I suspect it may be something to do with us having a lot of custom field values - my guess is that it's doing the ORM equivalent of a "SELECT * FROM custom_values" rather than parsing the list definitions.. but since custom values are all effectively free text fields in terms of storage, maybe this is fair.
The attributes form fetches these even if they don't apply to the current projects / tracker selection, so maybe some extra laziness there would be good, or maybe some extra efficiency on the Redmine end. Which begs the question.. should the Redmine end of this project be in the same tree as this end...
The text was updated successfully, but these errors were encountered:
Attribute update here takes around 17s
I'm not sure if this is down to the configuration of the repository, or if it's a problem on the Redmine side of the equation ; I suspect it may be something to do with us having a lot of custom field values - my guess is that it's doing the ORM equivalent of a "SELECT * FROM custom_values" rather than parsing the list definitions.. but since custom values are all effectively free text fields in terms of storage, maybe this is fair.
The attributes form fetches these even if they don't apply to the current projects / tracker selection, so maybe some extra laziness there would be good, or maybe some extra efficiency on the Redmine end. Which begs the question.. should the Redmine end of this project be in the same tree as this end...
The text was updated successfully, but these errors were encountered: