Only invalidate query cache when new data is ready #630

oyiptong · 2016-05-04T14:00:51Z

Instead of invalidating data before repopulating, only invalidate when new data is ready.

Due to some profiles being big causing queries to take 30+ seconds, one way to ensure this takes less time is to only clear the existing cache for a query when new data is ready.

…g first

oyiptong added Add-on platform Performance labels May 4, 2016

oyiptong self-assigned this May 4, 2016

oyiptong added this to the 7. RC 3 (May 6) milestone May 4, 2016

oyiptong added a commit that referenced this issue May 4, 2016

feat(caching): #630 replace data when ready as opposed to invalidatin…

49f6ca7

…g first

oyiptong mentioned this issue May 4, 2016

Improve cache invalidations #633

Merged

oyiptong added a commit that referenced this issue May 4, 2016

feat(caching): #630 replace data when ready as opposed to invalidatin…

b6cecfb

…g first

oyiptong closed this as completed in #633 May 4, 2016

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Only invalidate query cache when new data is ready #630

Only invalidate query cache when new data is ready #630

oyiptong commented May 4, 2016

Only invalidate query cache when new data is ready #630

Only invalidate query cache when new data is ready #630

Comments

oyiptong commented May 4, 2016