What happens when you're the #1 story on HN
jimplush.com
jimplush.com
I wish information like this was more forthcoming in other blogs like this.
It's funny when unintended changes and mistakes lead to better conversions. An example that comes to mind was PlentyOfFish's poorly resized images leading to higher profile clickthroughs since people wanted to see the images with correct aspect ratios.
Interesting article and discussion here: http://news.ycombinator.com/item?id=2049105
So many people do not realize this and then say that you have to wait a day before seeing any stats in Google Analytics. On the contrary you definitely can see instant results, the interface just doesn't make this as easy as it should be.
And yet it does all the time. It looks like this guy has a typical LAMP stack running on a Linode slice, presumably running a single query to return a single record and render it as HTML.
Even assuming that all 40k pageviews came in one single hour, that's still eleven requests per second, which gives you 100ms to serve each one. That's like years in CPU time. There's no reason that should even spike the CPU off of zero. There's definitely no reason you'd need to worry about caching for a load that small.
I just don't get it.
Is LAMP really that slow out of the box?
(sorry if you already know this & answered it in your previous comment. I just don't want others to miss out on GA's real time capability)
Officially they say that data won't appear until after 24 hours [1], but generally some of it will, but usually not all.
If you know the Analytics patterns of a site reasonably well (as I do my company's sites) then you can often look at the day's traffic and estimate how it's doing, but never expect it to be the final number.
(In some cases, I've actually seen traffic for the day go down after twenty four hours, once Analytics has finished working it out. I'm not sure why..)
[1] http://www.google.com/support/analytics/bin/answer.py?hl=en-...
FWIW, I had a #1 HN story that generated maybe 100 new subscribers out of 100,000 pageviews. I was impressed, however, by how many checked out the homepage to see other posts.
PS: I find putting ads on a personal blog to be a bad idea. Unless you blog for a living, the tiny revenue you might make from it is not worth the unprofessional appearance of displaying ads.
The only problem is that nearly every second ajax link in the admin times out. That's been broken for a long time.
I have an EE install on Linode with nginx and MySQL, so I was wondering what I could expect?
Caching. Rules.
Is it normal not to have to cache for HN + Reddit?
It's just good practice to cache when you can. There is no reason to ask the database for the same article 1000 times a second if it's not changing. I didn't feel the server was going to crash at that moment but I did notice MySQL was doing plenty of work it didn't need to.
The concern was if it got picked up by another site like digg or reddit then it could have been more of an issue.