I don't know which is the lightest. However there are quiet a few groups looking at getting squid to run in embedded platforms. OpenWrt and the Debian Embedded projects. I suspect that you will need to make a specific build with redundant features disabled. - In particular disable the memory cache and rely on the file-system cache
It just strikes me that if you already have Apache running - that adding mod_proxy would have a limited overhead as you already have most of the Apache code running for the HTTP server adding mod_proxy would not be a significant extra overhead, You can configure it to have no memory cache. The downside is that I don't think that you can configure it to auto preload/refresh the disk cache after-hours when the link is under utilised. I think that you can do this with squid However I think that there are other tools that would do this more efficiently in conjunction with mod_proxy. Over the weekend I will fire up a VM with 256Meg and see how well it goes --------------------------------- Chris Martin e: [EMAIL PROTECTED] m: +61(0)419812371 --------------------------------- -----Original Message----- From: Martin Langhoff [mailto:[EMAIL PROTECTED] Sent: Thursday, 25 September 2008 8:14 AM To: Chris Martin Cc: Mark Nottingham; XS Devel Subject: Re: [Server-devel] Squid tuning recommendations for OLPC SchoolServer tuning... On Wed, Sep 24, 2008 at 11:25 PM, Chris Martin <[EMAIL PROTECTED]> wrote: > Has any one considered using the proxy module in Apache HTTP server. > You are already taking the hit of running a web server, - the proxy module > just might give you enough features. > > Certainly you get Caching and Access Control I have considered it, and it is my second option if I cannot tame Squid :-) - apache2 is running, though with a few memory-heavy modules so to run a proxy I have to start a second daemon anyway (to keep the memory footprint under control). Only ever played with apache as a reverse proxy many years ago -- I have no idea how it fares as a general forward proxy, and whether it is comparable with squid under the kind of constraints I have. I do understand apache's memory model a whole lot better, but I am willing to learn Squid and tweak a bit if it's better. Within the constraints I have - do you have info/experience indicating apache would fare better or same? cheers, m -- [EMAIL PROTECTED] [EMAIL PROTECTED] -- School Server Architect - ask interesting questions - don't get distracted with shiny stuff - working code first - http://wiki.laptop.org/go/User:Martinlanghoff _______________________________________________ Server-devel mailing list [email protected] http://lists.laptop.org/listinfo/server-devel
