Describe the bug
As reported by @Nachiket18 , RunningWorkflow repeatedly calls Workflow.cellsAndModulesInOrder
Expected behavior
This is not a bug, strictly, but calling this function instantiates a large number of objects, which leads to a considerable slowdown in the scheduler.
Ideas to Fix
Have RunningWorkflow call a raw SQL query to avoid object construction overheads
Have RunningWorkflow become the canonical source of truth about workflow execution (and make it responsible for mirroring that state back into the database). This would mitigate many of the new objects that need to be computed.
Describe the bug As reported by @Nachiket18 ,
RunningWorkflowrepeatedly callsWorkflow.cellsAndModulesInOrderExpected behavior This is not a bug, strictly, but calling this function instantiates a large number of objects, which leads to a considerable slowdown in the scheduler.
Ideas to Fix
RunningWorkflowcall a raw SQL query to avoid object construction overheadsRunningWorkflowbecome the canonical source of truth about workflow execution (and make it responsible for mirroring that state back into the database). This would mitigate many of the new objects that need to be computed.