How does caching work in the video portal?

Kaltura's video portal uses caching to enhance performance. Different types of data have specific cache durations:

  • Media entries (individual videos, gallery lists): cached for 10 minutes
  • Categories and application-related data: cached for 30 minutes
  • User display names: cached for 24 hours

This caching follows a "time-to-live" (TTL) approach, meaning data is refreshed after its set duration. However, the system also proactively invalidates cache entries when related data changes, ensuring users see up-to-date information.

Can I manually clear the cache?

Yes. Administrators can clear the entire cache from the Configuration Management interface. Additionally, during module development, developers can specify cache durations for specific items and are responsible for invalidating them as needed.

Which actions are cached?

Most API calls are cached to optimize performance. However, certain actions, especially those related to user entitlements (like checking if a user has access to a category), may bypass the cache to ensure immediate updates. It's important to note that some API responses are cached per user. So, if User A performs an action, the immediate effect might not be visible to User B until the cache refreshes.

Why aren't changes from the Kaltura Management Console immediately visible in the video portal?

Due to caching, updates made in the KMC might take a few minutes to reflect in the video portal. To expedite this, administrators can manually clear the cache, ensuring immediate synchronization between KMC and the video portal.


Was this article helpful?
Thank you for your feedback!
User Icon

Thank you! Your comment has been submitted.

In this article
Related articles
Back to top

Never miss a thing!

Subscribe to our customer newsletter and our release notes updates, so you always get the best out of Kaltura.
Newsletter