Any word on how we're doing this week, ma'am?

I think it would suck for you guys if we suspended you every time you went over 50.

I don't think suspended is what Jesse was thinking of. It wasn't what I was, anyway -- since we can and have been suspended for overuse. But if *our* code could check the connection level and just tell some people to wait, or something. Well, there'd be a riot, but you get the drift.

The problem with putting people in a queue to be connected is that people at the back would just keep hitting "Read New" (or hitting "Refresh" or whatever) because their computer would be unresponsive. I think it would ultimately create more connections, and make everything reeeeeeeeeeeeeeally slow.

think it would ultimately create more connections, and make everything reeeeeeeeeeeeeeally slow.

Not if checking redirected one to a "too busy" page without using any connections at all.

No, I don't like the thought of doing that -- I'd rather rein the code in. But I get the point.

Yeah, that's what I meant. If the person trying to make the 31st connection just had to wait until one freed up or something. I dunno.

What would be better would just be to delay page requests until one of the 30 connections was free. But that's not something we can easily implement.

I don't think suspended is what Jesse was thinking of.

Okay. When Jesse said "the system" it sounded like she was looking for something on the server side that prevented users from going over. The only server side option is to suspend you. I mean, maybe you could code something that tracked how many users were logging on and posting and cut excess posters off but it sounds like something that would involve a lot of work. I'm not even sure it would be that effective.

Kristen, do you know, is there any kind of reporting on our server usage, that could at least key us in after the fact, when we've over used. Something that tells us our highs and lows, something that says we opened 80 unique connections at on 9/9/03, and only 20 at 11:30pm on the same day. Could we get some sort of daily report card? It might not pinpoint our problems, but it could help us narrow our focus.

For instance, if from 8pm Eastern to 11pm Eastern on 10/1/03, we found out we never went over, we could could be more certain our problem is our code than our usage. If on the other hand, we could line up our spikes with big events, like post-n-watch or a heated bureaucracy discussion, we'd have some affirmation that it's us, and not a technical issue.

Not as of this time. As I mentioned before, Steven is trying to find me a program that he can install on the server so I can monitor your usage remotely. But for right now, every time I want to check, I need to get in touch with Steven who needs to manually check.

Plei and I both created a boxed set thread. I closed and archived one of them, so only one shows up on the front page, but in Set Profile both are still listed as subscribable.

It might make sense to remove archived threads from the list-o-threads you see in Set Profile

Actually there's three Boxed Sets in set profile.