Ticket #5393 (closed defect: fixed)
journal updates are too heavy, should happen less often
|Reported by:||tomeu||Owned by:||tomeu|
|Priority:||high||Milestone:||8.2.0 (was Update.2)|
|Deployments affected:||Blocked By:|
Right now, the journal listens for changes in the DS and updates itself every time there's a create/update/delete.
Instead, when we are notified of a change,we should just invalidate the cache, and when the journal becomes active, update the UI.
Switching to the journal will be slower, but at least we won't be degrading general performance of sugar and activities.