Well, I emailed Steven to mention the change to the quote generator and asked him to let me know how much of a difference it makes over the next few days. I mean, if we were at say 150 connections, we should drop to 75 now.
Also, I agree it's worrisome. On the other hand, I can't see how we had 100 people posting at once, much less the same moment.
Shot in the dark. Do user sessions open connections to the database, or is that just strictly cookies and/or session variables?
Here's my last xpost:
Why not move ALL closed threads off this board? Leave them up for ONE WEEK, no more than that. Then we put the in "The Attic."
We could have them hosted by Fangeek, at a pretty minimal price (I know da owners, I'll haggle). That should lighten the "click through" load on the server, substantially. The threads would be available for read only, just not on this board.
They don't have to be here.
Speaking of the archives, are the subdomains working yet so that I can get to the archives ftp? And if so, what address do I use?
They are working again. If the FTP account is already set up, you should be able to login through ftp.buffistas.org.
DX, you should be good with the old address -- holler if not.
Assuming that the biggest trouble really is just that we occasionally have 100 people all calling the database at the same time--is there any way to limit that on our end, directly? Hit 50 open connections, and all subsequent attempts have to wait 5 seconds and check again? Or it is impossible to divorce the attempt from the actual connection? Or would such a solution be, in its own way, as (or more) taxing?
(It's been too long since I was actually studying this stuff.)
DX, if you want to email me how you're doing the archive stuff, I can take some of it on tomorrow, probably get a couple of threads done.
I think getting rid of auto-refresh could be a good idea too -- the number of people who would sit there going refreshrefreshrefresh would be, I'll guess, far less than those who just leave it up for an hour or two in the background refreshing every 10 minutes.
Also, we're going to see if we can further optimize the code, no?