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
Not blocking, but significant performance degradation for some customers
Version
Impacts creating releases on 2022.2, impacts all Git operations on 2022.3
Latest Version
I could reproduce the problem in the latest build
What happened?
On Octopus 2022.2 versions, creating releases takes a long time on instances with a lot of machines. On Octopus 2022.3, all Git operations are impacted.
Reproduction
On an Octopus 2022.3 version
Create ~3000 machines in an instance
Fetch a deployment process, deployment settings, or project variable set from a Git project
Request time will be very long
Error and Stacktrace
No response
More Information
When writing to and reading from OCL, we convert between slugs (or names on older version of Octopus) and ids. This allows us to have human readable identifiers in the OCL, rather than something like Channels-102, that wouldn't be particularly helpful to anyone looking through OCL files.
At the moment, the way that we load this data from the database is extremely inefficient. We're often loading a lot more data than we actually need to perform this mapping. For instances with a large number of machines, loading this data can take a long time.
Workaround
No response
The text was updated successfully, but these errors were encountered:
Team
Severity
Not blocking, but significant performance degradation for some customers
Version
Impacts creating releases on 2022.2, impacts all Git operations on 2022.3
Latest Version
I could reproduce the problem in the latest build
What happened?
On Octopus 2022.2 versions, creating releases takes a long time on instances with a lot of machines. On Octopus 2022.3, all Git operations are impacted.
Reproduction
Error and Stacktrace
No response
More Information
When writing to and reading from OCL, we convert between slugs (or names on older version of Octopus) and ids. This allows us to have human readable identifiers in the OCL, rather than something like
Channels-102
, that wouldn't be particularly helpful to anyone looking through OCL files.At the moment, the way that we load this data from the database is extremely inefficient. We're often loading a lot more data than we actually need to perform this mapping. For instances with a large number of machines, loading this data can take a long time.
Workaround
No response
The text was updated successfully, but these errors were encountered: