For a small home network, is there any point to running Squid? [closed]

For a small home network -- two laptops, two desktops, plus the main server -- should I expect much gain by running Squid on the main server? I fully understand the value of running a caching name server for a small home network, but I'm not sure if there is any value to running an HTTP caching proxy.

The main server does full NAT for all other computers on the network, in case it matters.

You probably won't really see much gains in network performance.

What you do get is

• A place where you can block annoying sites
• you can integrate clamav to help block malware before it gets to your windows systems.
• You can watch the access logs and see what computers are doing what. And possibly see requests from systems that where infected by malware. Or see when some stupid application is checking every 5 minutes for application updates.
• Protect the Kiddies from sites you feel are objectionable when combined with blacklists.

I don't think it's worth it. You might see a small speed-up on commonly used pages (if they're used by both machines), but you're not going to save enough bandwidth or time to make it worth the hassle, IMO.

If you have a small network, there's not much to be gained. I've had squid running on our home network. Last time I measured it, it was reducing the traffic by 6-8%. There's also the gain you get by removing the effect of latency on TCP setup. But unless multiple users are hitting the same site, the re-visit hits are likely as not going to come from your browser's cache anyway. If I didn't know the squid was running I'd be hard pressed to tell the difference.