It's not, correct me if I'm wrong, ita, that creating more threads causes database problems, but simply that experience shows that having more threads means there's more traffic.
Yes. The table of posts is what Hostrocket says is too large.
We open it up, we talks the talk, we votes, we shuts it down. This thread is to free up Bureaucracy for daily details as we hammer out the Big Issues towards a vote. Open only when a proposal has been made and seconded according to Buffista policy (Which we voted on!). If this thread is closed, hie thee to Bureaucracy instead!
It's not, correct me if I'm wrong, ita, that creating more threads causes database problems, but simply that experience shows that having more threads means there's more traffic.
Yes. The table of posts is what Hostrocket says is too large.
I can't figure if you're correcting me because I'm wrong or saying I'm right.
There's one central table for all posts, which are just marked as belonging to a thread, rather than a table for each thread?
But didn't somebody run numbers that suggested that there was a strong causal correlation between numbers of threads and numbers of posts?
That is, you have 3 threads, you have 3000 posts; you have 4 threads, you don't have 3200 posts, you have 4000. (Numbers pulled out of Stephanie's frog-whistle.)
didn't somebody run numbers that suggested that there was a strong causal correlation between numbers of threads and numbers of posts?
I kind of said that, though not in so many words. More threads does not dissipate the same number of posts over a wider area, it increases the overall number, yes.
But if there's a fundamental issue where more posts means more instability, then we have to deal with it sooner or later anyway because the number of posts in that table will always get bigger unless they're actively removed in some way.
They're being actively removed.
Our database is large by HR's standard, and our posts database is most of that.
It was decided to archive many of the Natters, and I'm halfway through the accompanying coding effort to reroute links to those threads.
How will 6 certainly win?
Because, I mean, I've gotten a very strong vibe from this thread that the 6 people comprise a larger group than either the 3 people or the 4 people, if taken separately.
edit: and your ballot totally cuts out people who think 4 is fine, but 3 is too short, and would therefore vote for 4 first, but for 6 in a 3 vs 6 runoff.
... yes. That's a weakness.
I actually think that would unfairly penalise 6 months. See, if we go with that option, 6 would need to get over half the primary votes to win. The other two options only need to win a preferential ballot.
And I was saying that that kind of was fair, because, as I was seeing it, 3 and 4 are much more similar to one another than either of them are to 6.
But, you know, OK, so that quasi-preferential ballot of mine has those weaknesses. I really think we ought to go with an actual preferential thing. I'm with Jon.
I'm with Jon.
Wow! Thanks, Rebecca.
I'm with Jon.
Do you mean you're backing John?
Because, I mean, I've gotten a very strong vibe from this thread that the 6 people comprise a larger group than either the 3 people or the 4 people, if taken separately.
But if, as you say, the 3-or-4 people would all choose one of those as the first choice, and the other as the second choice, then the only way 6 will win on the preferential ballot is if more than 50% of the voters vote for 6 as a first choice, in which case 6 definitely should win.
t edit: OK, and now that I actually finished reading your post and realized that you're supporting preferential, I see that this entire post is completely pointless argument.
I would like to express that I believe 6 is the one true number. Except for 12, which is already dead. If 6 fails, I would vote for 3. Because splitting the year into thirds seems really really odd to me.
So advocating for 3 as opposed to 4, even though I support 6 is completely logical.