I'm a bit late on this one, since nobody had mentioned anything to me about MySQL 4.x. Either way, I'm against it at this point. Mainly because the bottleneck is not with our MySQL server, it's with bloated httpd procs.
Slash and scoop together with multiple sites requires a horrendous amount of resources. And I care about the data.
--
One future, two choices. Oppose them or let them destroy us.
Yes and no (Score:2)
Slashdot does use the Inno tables though. They scale very well.
So, MySQL Max 3.23.X yes, 4.X, if you don't care about your data.
--
You can't grep a dead tree.
Re:Yes and no (Score:1)
"How about you interface with my ass? By biting it!" --Bender
Re:Yes and no (Score:2)
It solved a lot of problems the Slashdot had.
--
You can't grep a dead tree.
Re:Yes and no (Score:1)
I concur.
I'm a bit late on this one, since nobody had mentioned anything to me about MySQL 4.x. Either way, I'm against it at this point. Mainly because the bottleneck is not with our MySQL server, it's with bloated httpd procs.
Slash and scoop together with multiple sites requires a horrendous amount of resources. And I care about the data.
One future, two choices. Oppose them or let them destroy us.
Parent