a) I'm making the code run solid in safe mode and b) I'm switching the threads to each have their own table.

a) is just a good idea, and I should have already done it. b) should hopefully speed things up as no post table will go much over 10,000 records, and a crash of posting in one thread should have less impact on posters in other threads.

I'm also on the path to making sure all the admin functions are coded--there are a couple I'd poke straight in the database for--thread sequencing in a folder, for instance, and a page to create and edit thread folders. I've done the latter.

Excellent! I like the b) move a lot. I don't know enough about safe mode to have an opinion, but it sounds... safe.

I have an image of ita wrapping different lines of code in teeny, tiny condoms.

The site's going to be slow tonight while I run the test conversion.

Is anyone else still having big-time lags even now?

ETA: Looks like it zipping along fine now. It just took a few minutes to post my last message, and I got a fail error before then when I was trying to access Natter.

The board was normal speed all day for me, until the past 10-ish minutes, when it dropped to comatose. It took about 5 minutes after clicking on the link to this thread for the thread to even open.

t edit Okay, and that post took literally 10 minutes to post.

It *was* zipping along for me earlier, and now it's back to huge lag times.

That was my fault. My work on the test site put a *much* bigger load on the server than I expected. I'll defer the rest until after 10pm board time.

The lag for a good cause is fine. When watching the hourglass we can think "stuff is getting fixed" rather than "stuff is broken."

Soliciting more testing: This time the playground is buffistas.net, with a snapshot of b.org that's a few days old. So you can login there with your current ID and password as of three days ago.

Please stop by and try and break any and everything. Report there in the BBABB++ thread.

Thanks!