Matthew, I believe be interesting know better your environment, btw, you can work with proxy (between your company and filial/client) or really use Spacewalk Proxy. With this you will probably work better, you have to check the necessity according the quantity of clients or the problem caused by latency.
Do a test with one proxy in your problematic environment and enjoy! Let me know if works for you. B'Regards ______________ Atenciosamente Waldirio msn: [email protected] Skype: waldirio Site: www.waldirio.com.br Blog: blog.waldirio.com.br LinkedIn: http://br.linkedin.com/pub/waldirio-pinheiro/22/b21/646 PGP: www.waldirio.com.br/public.html On Tue, Nov 18, 2014 at 2:20 PM, Matthew Madey <[email protected]> wrote: > All, > > I've run into a situation where my total metadata for channels has grown > quite large (about 200MB). I've done all I can as far as channel\package > management to reduce the size of the metadata.. > We have a number of locations where the bandwidth to the clients is > extremely small.. So downloading new metadata causes severe network latency > on these clients.. We've done some traffic shaping on the network layer to > reduce the impact, but I'm looking for other alternatives focused more > around Spacewalk. Looking for anyone who may have a similar situation and > what steps they've taken to mitigate the issue. Are there any sort of > throttling settings available in Spacewalk, or does this all have to be > done at the OS\Network layers? > > > > _______________________________________________ > Spacewalk-list mailing list > [email protected] > https://www.redhat.com/mailman/listinfo/spacewalk-list >
_______________________________________________ Spacewalk-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/spacewalk-list
