Currently all the timer tasks are deleted during processing within the transaction, but some of the immeidate tasks are deleted during execution, but some are after, using a commitTimer to batch deleting.
The batch deletion is hard to understand and actually not going to be performing well for NoSQL databases that don't have Global Secondary index. (the tasks table partitioning will be based on processId, not shardId)
Currently all the timer tasks are deleted during processing within the transaction, but some of the immeidate tasks are deleted during execution, but some are after, using a commitTimer to batch deleting.
The batch deletion is hard to understand and actually not going to be performing well for NoSQL databases that don't have Global Secondary index. (the tasks table partitioning will be based on processId, not shardId)