Friday, October 27
Currently receiving 2000+ trackback spams per minute.
Had to reconfigure Apache, which was choking under the load. Bloody Apache 1.3. Bloody CPanel. Grrr.
Wednesday, October 25
It's good to be home.
Friday, October 13
When I look at a Linux server, I don't want to see hundreds of megabytes of memory free. At least, not on a busy web/database server with several gigabytes of actively used files.
All that memory should either be used by programs or for caching files. If there's 500 megabytes free, that means that 500 megabyes of memory was being used by programs that have now exited. The only thing that should be using 500 megabytes of memory is the MySQL server, and that (for obvious reasons) should not exit.
One big culprit is Movable Type. On our database, the MT comment script can use 60MB of memory; the search script used 300MB until I replaced it. A spamming run can easily fire up ten comments simultaneously (since they are not only extraordinarily inefficient in terms of memory use, but also in terms of speed). Then Fluffy kills them, and I'm left with a 600MB hole unaccounted for.
Another one is the Analog web stats package. I've just disabled it system-wide because it was using 300MB of memory to produce the stats for a single web site. (I've forgotten which one, but not one of the big ones like Ace or the Jawas.)
And then there's Apache. Leave it alone on a server with PHP and CGI and all kinds of other crap running, and you'll soon find individual Apache worker processes using 40 to 60MB each. If you have a hundred of those, that's 4 to 6GB of memory gone, which is probably more than you actually have.
Of course, if you're not running CPanel, you're probably running something reasonable like Apache 2.2 or lighttpd or, well, anything other than Apache 1.3.
Anyway, something is flushing useful data out of memory, and something is slowing down my blog, and I think it's the same something.
So until morale improves I'll be lining the suspects up against the wall and shooting them one by one.
(Minx itself is an interesting case. It's using 152MB of virtual memory for 10 threads, but only 15MB of that is resident. Why it does this I don't know, but unless I enable Psyco, the resident size never increases.)
What is it with these guys?
They show up, download 5GB from a website that only has 300MB worth of files, and disappear.
Sure, I now have 4TB of bandwidth to play with, but that doesn't mean I'm happy for these idiots to just burn through it like that.
Tuesday, October 10
I'm assuming that they're banking on a 100:1 oversell - which is probably reasonable. I wonder what they would do if I actually started using that 2TB every month...
Update: Seek and ye shall find. Dreamhost blog: The Truth About Overselling.
Sunday, October 08
Disk drives are not supposed to go "beep".
Saturday, October 07
The failure stopped being intermittent.
57 queries taking 0.3734 seconds, 303 records returned.
Powered by Minx 1.1.6c-pink.