Thank you! Changes are made.

Cool.

Jesse--due to bugs there are three entries on the links page to amazon, to two different addresses--how is it that you wanted them displayed?

Yeah, no. But my computer here at work is literally trying to kill me, so I'll need to figure it out from home.

Okay, twice now this morning, I have had the "Post Message" button dump me onto page one of whatever thread I was in (once in Natter, once in Bitches), and not process the post. I had to go back to the post page and hit the Post button again (thank you, text-saving Safari browser!) to make my posts.

And the board has been running agonizingly slow for me for several days. I know, this is useless information, but it's all I've got -- something seems to be wrong with the board (this weird Post Message behavior, if nothing else), but I don't know what else to say when I'm not getting helpful error messages.

Sean, can you go up to our BugTracker and enter that--and don't forget to include browser and OS type and version information.

I would love to be part of a new LAista list, fwiw. I don't expect us all to be best friends, but it would be nice to get together now and then.

t /annoying cry baby

The board is super-slow today. Here's a snapshot of what's going on on the system:

Cpu(s): 4.7% us, 2.0% sy, 0.0% ni, 0.0% id, 93.3% wa, 0.0% hi, 0.0% si

That "93.3% wa" is I/O wait, which means that the system is spending 93% of its time reading and writing to the disk. Basically, the CPUs are sitting mostly idle while they wait for disk reads to complete. Basically, MySQL is thrashing the system.

Things we could try that could fix things in the short term are:

• Running any of CHECK TABLE/REPAIR TABLE/OPTIMIZE TABLE on the posts table.
• Archiving and deleting a bunch of stuff from the posts table.
• Making extra sure that everything is indexed like it's supposed to be.

I couldn't tell a damned thing. The whole internet is thrashing for me today.

Last time were were severely slow I went through the queries and checked the indices and MySQL wasn't complaining, so I ruled that out as a major contributor.

We've had a lovely luxury of not archiving in the longest time--so you have a sense of the size of this database compared to other MySQL databases? Are we that big?

I can check table later tonight unless you think it's very urgent.

I don't have enough experience with MySQL to know how big is too big, but we're closing in on a million rows in the posts table.

[edit: and it took me 15 seconds to run a "select count(*) from posts" query]

This feels sudden and I don't like that one bit. But archiving can't hurt.

DX? You around?