I'll need to review with the dev team for their input. Cache storage is currently managed by timeout instead of cache size. I would like to understand why it was done this way instead of specifying cache size. In the documentation, it suggests managing size by setting shorter timeout periods for the cache.
Depending on available storage capacity of the selected device, the cache expiration period specified by viewing.cacheLifetime in central configuration may need to be shortened to accommodate cache load.
Regular cache, I think they can already manage pre-conversion cache using the timeout settings? And we wouldn't want to delete pre-conversion items to clear space if it hasn't timed out yet, so I don't think a space based control method would make sense there.
Josh Letcher
I'll need to review with the dev team for their input. Cache storage is currently managed by timeout instead of cache size. I would like to understand why it was done this way instead of specifying cache size. In the documentation, it suggests managing size by setting shorter timeout periods for the cache.
Attachments Open full size
Regular cache, I think they can already manage pre-conversion cache using the timeout settings? And we wouldn't want to delete pre-conversion items to clear space if it hasn't timed out yet, so I don't think a space based control method would make sense there.
Attachments Open full size
Which cache - pre-conversion cache or the regular cache?
Attachments Open full size