Home/ Questions/Q 1102193
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-17T01:08:54+00:00

I have a large data set that is updated once a day. I am

  • 0

I have a large data set that is updated once a day. I am caching the results of an expensive query on that data but I want to update that cache each day. I am considering using CacheItemRemovedCallback to reload my cache on a daily interval, but I had the following concerns:

  1. Isn’t it possible that the CacheItemRemovedCallback could be called before my expiration (in the case of running out of memory)? Which means reloading it immediately doesn’t seem like a good idea.
  2. Does the CacheItemRemovedCallback get called before or after the item is actually removed? If it is after, doesn’t this theoretically leave a period of time where the cache would be unavailable?

Are these concerns relevant and if using CacheItemRemovedCallback to reload your cache is a bad idea, then when is it useful?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    From everyone’s responses and from further reading I have come to the following conclusion:

    My concerns are valid. Using CacheItemRemovedCallback to refresh cached items is not a good idea. The only practical use for this callback seems to be logging information about when your cache is removed.

    It seems that CacheItemUpdateCallback is the more appropriate way of refreshing your cache on a regular interval.

    Ultimately, I have decided not to use either of these calls. Instead I will write a service action so the database import job can notify my application when it needs to refresh its data. This avoids using a timed refresh altogether.

    • 0