Improve Action Cleanup Mechanism
Feature description
Currently actions used for allowing users to do undo/redo are deleted by default after 2 hours of not being updated. This means if you leave your tab for two hours, come back and try to undo it probably wont work anymore due to the cleanup. Our main worry is that we many users performing actions the table might become massive and the cleanup is needed regularly to prevent slowdowns. Additionally the field updated action stores metadata which is often the entire column/m2m table to do the backup and so by not cleaning this up lots of space might be used. To procede I believe we need to know:
- What are the performance impacts of a huge action table
- What are the storage impacts of a huge action table
Then we can decide if we need to adjust the mechanism to cleanup more, perhaps by only allowing 100 actions in your undo/redo buffer at any one time.
Alternatively if the peformance/storage impacts are neglicable we could instead switch to a more user friendly implementation that only clears the sessions actions when you close the tab or logout.