Thanks Sent from my iPhone
> On Apr 23, 2024, at 00:41, Amos Jeffries <squ...@treenet.co.nz> wrote: > > On 22/04/24 17:42, Jonathan Lee wrote: >> Has anyone else taken up the fun challenge of doing windows update caching. >> It is amazing when it works right. It is a complex configuration, but it is >> worth it to see a warm download come down that originally took 30 mins >> instantly to a second client. I didn’t know how much of the updates are the >> same across different vendor laptops. > > There have been several people over the years. > The collected information is being gathered at > <https://wiki.squid-cache.org/ConfigExamples/Caching/WindowsUpdates> > > If you would like to check and update the information for the current Windows > 11 and Squid 6, etc. that would be useful. > > Wiki updates are now made using github PRs against the repository at > <https://github.com/squid-cache/squid-cache.github.io>. > > > > >> Amazing stuff Squid team. >> I wish I could get some of the Roblox Xbox stuff to cache but it’s a night >> to get running with squid in the first place, I had to splice a bunch of >> stuff and also wpad the Xbox system. > > FWIW, what I have seen from routing perspective is that Roblox likes to use > custom ports and P2P connections for a lot of things. So no high expectations > there, but anything cacheable is great news. > > > >>>> On Apr 18, 2024, at 23:55, Jonathan Lee wrote: >>> >>> Does anyone know the current warm cold download times for dynamic cache of >>> windows updates? >>> >>> I can say my experience was a massive increase in the warm download it was >>> delivered in under a couple mins versus 30 or so to download it cold. The >>> warm download was almost instant on the second device. Very green energy >>> efficient. >>> >>> >>> Does squid 5.8 or 6 work better on warm delivery? > > There is no significant differences AFAIK. They both come down to what you > have configured. That said, the ongoing improvements may make v6 some amount > of "better" - even if only trivial. > > > >>> Is there a way to make 100 percent sure a docker container can’t get inside >>> the cache? > > For Windows I would expect the only "100% sure" way is to completely forbid > access to the disk where the cache is stored. > > > The rest of your questions are about container management and Windows > configuration. Which are kind of off-topic. > > > Cheers > Amos > _______________________________________________ > squid-users mailing list > squid-users@lists.squid-cache.org > https://lists.squid-cache.org/listinfo/squid-users _______________________________________________ squid-users mailing list squid-users@lists.squid-cache.org https://lists.squid-cache.org/listinfo/squid-users