@tsteur opened this Pull Request on February 16th 2020 Member

I know the code is not ideal since everyone who calls forgetRememberedArchivedReportsToInvalidate would need to know to ideally also invalidate the general tracker cache. On the other side we're seeing quite a lot of invalidations like sometimes 50 invalidations within a few ms causing heaps of cache invalidations and cache re-generations across many servers within few ms potentially resulting in locks and temporary performance issues.

Maybe this helps to prevent also things like #15545

@diosmosis maybe you can have a look? Maybe since the code is only used internally it may be fine like that?

@diosmosis commented on February 16th 2020 Member

Looks good to me, some suggestions:

@tsteur commented on February 16th 2020 Member

@diosmosis removed the other clear cache as well 👍

This Pull Request was closed on February 17th 2020
Powered by GitHub Issue Mirror