We had refreshes every few seconds for a few things but these turned out to be a resource hog. Maybe it could work with updates every minute or even less often? That may mean times lag behind but it should be good enough. @dpschen Do you have another idea?
Can you do some sort of a compromise based on how far away the due dates are? If there we’re mentioning timespans in seconds, then check every 10 seconds or so, but if we’re mentioning minutes, then check once a minute, hours for hours, etc.
The thing is, we don’t know how far away a due date is until we check it. And it’s the check interval that’s taking up resources. A compromise would be a check every minute or something like that. I guess we’ll just implement different intervals and see which one has the best performance.