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
The current activation queue has some issues. It rearranges the order of activations and incurs noticeable additional costs.
By implementing a blunter and "simpler" queue, we can overcome these issues and achieve better performance compared to the previous queue.
Goals
Develop fast ring queue
Verify the queue model using Spin
Use new queue by default
Tasks
1.25d Verify queue model with slow methods [25.11]
(model code must be committed)
2.33d Verify queue together with fast methods and ensure that we catch known issues [27.11]
(model code must be committed)
2.33d Verify model of the fixed queue [04.12]
(fix the queue if issues are found, model code must be committed)
2.33d Test the fixed queue on benchmarks [06.12]
1.06d Merge all changes into stable [06.12]
0.46d*3 Enable on loaded pre-production databases [16.12]
1.21d Enable on some non-critical production databases [17.01]
3.83d Enable on all critical production databases [24.01]
1.06d Enable by default everywhere through code [03.02]
Description
The current activation queue has some issues. It rearranges the order of activations and incurs noticeable additional costs.
By implementing a blunter and "simpler" queue, we can overcome these issues and achieve better performance compared to the previous queue.
Goals
Tasks
(model code must be committed)
(model code must be committed)
(fix the queue if issues are found, model code must be committed)
Issues
Definition of Done
The text was updated successfully, but these errors were encountered: