On Mon, 5 Mar 2012, Erik Christiansen wrote:
On 05.03.12 19:05, Craig Sanders wrote:
1. run a local resolving name-server - bind9 or dnsmasq or something.
this makes a *huge* difference.
Now that looks like advice to follow, even if I have to resort to the O'Reilly DNS book which I haven't opened in a decade or more. ...
Under a susgestion from I think Russel Coker I use pdnsd. This only required minor (Note 1) editing of the config file to get it working. I was most impressed with the improvement in loading times.
2. run a local web proxy (e.g. squid or apache/nginx/whatever in proxying mode) to cache images, scripts, etc from frequently visited sites.
just as with DNS, having a local cache of recurring elements like images on a page from a local cache can massively improve the responsiveness of web sites.
Now you're talking turkey. I'll have a go at that. (Have done DNS before, but not squid.)
I'll probably keep it simple, at least to begin with, since that's easier if it doesn't work immediately.
Thanks a lot Craig, for the detailed advice, all of it very helpful.
Erik
I have thought of setting up something like spuid for a long time but I do not do much general browsing considering outside of Linux and a number of mostly text based railway sites the majority of the internet to be a major waste of time. Note 1: I have been using Linux since 1993 so my deffinition of minor may not be some one elses. Lindsay