Hi guys,

Thought I'd post this in here. If you know what "editing your hosts" file means keep reading.

I'm running a new front end server which at the moment balnacing requests to the main web node. Along the way it's going to try and cache what it can and give you correct expiry headers.

I could do with a few more people hitting it to make sure it's actually working as expected. I've not managed to break it yet despite some hard ab benchmarking.

So if you want to help out (pretty please) then could you edit your hosts file to this:Clicky >> gist: 235374 - GitHub

Could you report all issues on this thread only please, unless it's borked...

Done mine as well, no issues as yet

Things appear to be just as they should be to me

Well it works, and no oddities as yet, will keep it here for a few days see what happens.

EDIT:

Ok it's really slow, in a laggy kind of way in a couple of places when using the host.

Further update, that seems to be only when reloading a few pages at once.

Edited 15 November, 200916 yr by cheezemonkhai

Cheers guys.

It should never be any slower, well perceptably as it's all on the same hardware. On occasion it might slow if the main web node is busy or the db is. We're still on a single master sql box, so one big search can slow everything else down. With 100+users on it might be just that unfortunate to hit.

However I also note some swap has ben used on the new node. I'll look into that :(

seems to be ok for me.

502 Bad Gateway

nginx

Had this just now, but think it was both systems.

If you inspect the return headers, you'll see a X-cache HIT or miss reference. You should also get an X-Varnish id

Hopefully you'll also find that for everything that's a HIT youre browser does cache it.

For example

Cache-Control:max-age=2592000
Connection:keep-alive
Date:Sun, 15 Nov 2009 23:01:10 GMT
Expires:Tue, 15 Dec 2009 23:01:07 GMT
Last-Modified:Mon, 14 Sep 2009 14:47:25 GMT
Server:nginx
Vary:Accept-Encoding
Via:1.1 varnish
X-Cache:HIT
X-Varnish:1904419709

502 Bad Gateway

nginx

Had this just now, but think it was both systems.

You'll have caught me restarting the cache, had a bad conf and it took me a few seconds to fix the typo.

Going to leave it now, see how we go overnight.

Just added it