MediaCache mediaCacheOnStartReloadCache problem

[skyshade]

Hello,

We are making some tests with MediaCache plugin, and we notice that cached content is lost on every Wowza restart.

We saw in forum recomendation to use mediaCacheOnStartReloadCache and its works, but only for small cache. We made tests with 100GB cache with more that 200 thousands of objects, Wowza stuck in "MediaCacheImpl.start[MediaCache]: Loading cache: start -" for more that 2 hours.

The worst is that Wowza do not answer any requests during that fase, only logs:
"MediaReaderH264.open[1]: java.io.IOException: MediaCacheRandomAccessReader.open: Item not in cache:"

And drop user connections, lockdown media cache and this virtual host during cache reload.

Take 2 hours to reload cache is a pain, lockdown server during that is a pain ˆ2.

There is any workaround for this case? There is anything on medicache roadmap to handle this case?

[charlie]

There is no workaround. We have no plans to change this behavior. That is why the default setting is to not reload the cache. We have no short term or medium term plan to address this. We suggest that you flush the cache on start.

Charlie

[imartins]

We intend to use the mediacache for many TBs of cache with millions of objects in a server in Brazil getting content from S3, cache flush on every restart is impossible in this scenario.

Other proxy cache system like squid, apache, nginx use persistent cache seamless.

If mediacache can't do that we are thinking in use some like that:
{http origin server}<{squid<mediacache}

So mediacache will connect to a http proxy cache like squid on same server and this service will get content form origin. Do you think this model will work?

Thanks Charlie

[charlie]

Using another caching server inbetween is fine. I would not suggest using squid. I do not believe it handled byte requests very well.

Charlie

[imartins]

We made some tests with a http proxy cache inbetween and Wowza with tiny cache storage. Our results shows Wowza 80-100% more resources in that scenario, even with a large cache storage we have a poor performance. We intent to use this for a CDN scenario, we know that others CDNs user Wowza solutions. Do you know how they handle this cases?