Reduce Schedule-related DB Calls #181
Labels
No labels
Bug
Cleanup/Refactor
Core Feature
Documentation
Feature
Performance Improvement
Security Improvement
UX/Accessibility
Unreproducable Bug
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Blocks
#164 Tweaks and Fixes
rainbownapkin/canopy
Reference: rainbownapkin/canopy#181
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Certain scehdule functions, especially rescheduling multiple pieces of media, can take longer than they should due to excessive database activity.
In worst case scenarios, such as ending a stream in pusback mode with a days worth of media to re-queue, the server can sometimes even hang, temporarily refusing to respond to web-requests.
added #164 as parent issue
changed the description
Optimized queue.removeRange():
dd36b1d923Currently rolling on a verbose queue again to track saves. DB schedule processing now happens pretty fast, just need to send the queue out after large crunches instead of during to make it look quicker on the client end.
Finished optimizing automated queue transactions:
75301ec7d9Remove-range and pushback livestream end methods now run near-instantaneously on reasonably sized schedules.