No, there is no plugin for this. And no the db structure will not be changed.
Multisite is used for WordPress.COM which hosts 20 million blogs. With that same table structure.
No, no plugin for this that I know of, nor will it be in a future version. This is intended behavior. Each blog is separate content, hence separate tables.
Andrea_r:
Yes, but WordPress.COM probably uses hundreds of database servers and distributes the blogs between them, i think using the HyperDB plugin or in a similar way. I have to use the same database i have now (an SQL Server cluster of two nodes), and i don’t want to administer a DB with 27000 tables.
And i’m sure adding the option to mix all the blogs in the same tables wouldn’t be too hard.
If you’re supporting 3000 sites on your Network, you need multiple databases (and probably a dedicated server). Or fewer sites on the network, if you’re unable to support that.
Yes, wordpress.com uses Hyperdb. there’s also shardb, which will spread your exisiting db tables across multiple dbs.
http://wordpress.org/extend/plugins/hyperdb/
http://wordpress.org/extend/plugins/shardb/
And like Ipstenu said – if you really have 3K blogs… multiple dbs is the way to go. really.
Even administering 16 datababses is easier than one monstrous one.
(take the advice from the been there done that department)
I made a mistake, it is 12K blogs, not 3K. The current database is doing fine with that number of blogs, plus 4K galleries and about 400 forums all mixed in the same tables (as Community Server does). The posts table has 2.5 million posts in total and the database is 85Gb in size.
Performance of the forums is not the best, but that is because of the original queries of the product (which also is an old version). Blogs (which have some queries optimized by me) perform fine.
The posts table has 2.5 million posts in total and the database is 85Gb in size.
I would look into splitting that. We run a ginourmous database (nearing up on a couple TB if I added it all up probably), which we split into 100G chunks, but that’s on a dedicated slice and a crazy redundant setup. Point is this: You’re big. You need to start treating the database like the pretty princess it is 🙂
Bear in mind, I think that MySQL has a default 4G limit for each table, so you should probably get on that before you see ‘table is full’.
I don’t use MySQL but Microsoft SQL Server 2005 Enterprise in a dedicated three node (not two as i said before) cluster (8 cores and 32Gb RAM each). With MSSQL database limits i don’t need to change the architecture, and only scale horizontally (or vertically) when needed.
*blink* You do know that WordPress isn’t supported on anything by MySQL, right? I actually didn’t know anyone who’d managed to get it working (though my experience with that is well over a year old with a failed attempt).
If that really is working these days, which is cool, I would speculate that the sharDB and other splitting stuff may not work, since they assume MySQL.
If you are interested 🙂 you have information here:
http://wordpress.visitmix.com/
