I believe there is a problem with 'pre-caching' the podcast image and 'info' data, because it generates a large number of simultaneous feed requests which potentially overload the server. It's not a problem on my iMac, but that has rather more power than a Raspberry Pi, etc.
That could indeed be a problem.
I have worked up some proof of concept rough patches that I could share via gitHub. Basic approach is to limit the number of requests, and ensure podcast summary info is cached for a reasonable length of time. I'd make a PR if they advance beyond proof of concept.
Did you look into using Slim::Utils::Scheduler? Or Async::Util::amap() (see https://metacpan.org/pod/Async::Util - it's part of LMS). That those requests under control. The latter allows you to run a callback for each member of a list, with control about how many tasks you want to run "in parallel".
_______________________________________________ Squeezecenter mailing list [email protected] http://lists.slimdevices.com/mailman/listinfo/squeezecenter
