Over the last few weeks, we have been testing the use of Varnish on one of the web sites I work on – and the results appear to be fantastic – with a few false starts in the configuration. While I am not the one in the trenches configuring it – the potential performance and control we will have over our previous caching methods is quite frankly amazing.
If I could give you stats or more information I would, but at this time it is not a good idea.
I have been using Charbeat and Google Analytics for quite a while now an have only recently really started to look at Google’s Real-Time features. Yes, sure they are still in beta, but what at Google isn’t in beta. Today on one of the sites I work on we had a slashdot effect link [take your normal day’s traffic, multiply by 1000 and condense into an hour] and I was monitoring both Chartbeat and Google at the same time. For the first hour there was no comparison – we had exceeded our account size and only Google was showing me ‘true’ numbers.
If you are not familiar with xkcd, I suggest that you run over there right now and spend the rest of your day going through the archives. Some of the funniest, geeky cartoons can be found there – and it is updated frequently.
Apache Server overload – sometimes it feels like I spend half my working week dealing with this issue. Mockyblog has written up a handy little summary of how to approach this issue on small Linux servers. I think following Alex’s steps as a first line of fire in these situations would be very good advice. The article will also teach you some pretty basic lines of attack and methods of determining what exactly is going on with your server. I have used most of his suggestions in the past, but the post did teach me a couple things that I did not know before.
I would say this is must reading for those just getting started in the hosting world.
Code Standards, something I am really missing in my current position. At the moment everything is about speed, speed, speed. Deployment now, or forever hold you peace!
Okay, maybe it is not that bad, but there is definitely some room for improvement. One of our biggest tasks at the moment is maintaining legacy code and in this code there very little use of ‘standards’ and it is really killing our production time.