Simultaneous consolidations result in extreme performance degradation?
Summary:
We're noticing extreme performance degradation when users start multiple consolidation jobs before one job has finished.
Is this something that can be avoided? (without Groovy)
Content (please ensure you mask any confidential information):
One of our clients is working on their budget process and is noticing extreme performance degradation when multiple consolidation jobs are running simultaneous.
Example:
- Standalone consolidation of Actual or Budget, for one period, takes 8 minutes
- When a consolidation for Budget is started during a consolidation for the Actual scenario, the two consolidations take more than 8 hours.
We've seen this at multiple customers and are trying to convince them to check jobs before starting a consolidation. But only an admin can see all jobs, so that won't help most of the time.
Tagged:
0