One of my friend wants to install hundreds of drupal sites (nearly thousand) using drupal multisite feature. I have earlier used multisite for many of my clients projects and my own but for his particular request I think he will greatly benefit from the answers from the community.
What my friend needs is multisite install on a single database. I am not sure why he is very much particular about the single database but he wants all the thousands of the site to on a single database. Each instance of drupal will have more than 100 tables in his setup. So if he install 1000 sites in a single database, it should come to 100000+ mysql tables. A few sites or a few hundreds, the method of drupal multisite install is going to be the same but I want to know
what is the performance implication?
What are the additional precautions/steps need to be taken?
How difficult or easy is to backup/migrate/sync (master/slave) a database of this size?
I read the million-table blog post http://bobfield.blogspot.com/2006/03/million-tables.html and it seems interesting but all those tables are dummy and there is no real data in them. So I cannot actually compare my situation with them.
Thanks,
neokrish
Comments
*_*
Your friend must be wasting internet resources and must be occupying the domains so S/He can sell it later for better deal.
S/He should not do that.
Regards.
🪷 Beautifulmind
beautifulmind, my friend is
beautifulmind, my friend is NOT doing that for sure. He is genuinely looking for some multisite solution on which his ethical business depends on. thanks for your concern anyway.
100.000 MySQL Tables???
I personally would not trust on this setup...
Go with PostGreSQL...
If you or your friend need a good SysAdmin to help on the task of automate the building process for all this sites, or manage/administer the server, let me know! :)
Why PostGre? and why not
Why PostGre? and why not MySQL? doesn't mysql support large number of tables? Thanks for your suggestions. I will research on your suggesstions.
Thanks,
neokrish
If you have a machine that is
If you have a machine that is capable of hosting 1000 stand-alone database-driven sites, and a database server capable of serving those sites effectively, then the part of Drupal that distributes the job to the multisite instances will not be a bottleneck as far as I can see.
Take a normal drupal site and its recommenced requirements, multiply that by a thousand, buy a machine, and you are done.
(It's actually not that bad - but it could be, depending on your actual job.)
Of course a much more sensible idea would be to look into scaling out into manageable sized silos and looking into load balancing or whatever, but I can't tell from your description whether you are intending to do anything at all sensible.
If you describe what you are actually trying to achieve then there are probably better strategies. Look at what the guys from workhabit can help you with. They are pretty good at that stuff.
.dan. is the New Zealand Drupal Developer working on Government Web Standards
I'd suggest that your friend
I'd suggest that your friend perhaps has a popular misconception about multi sites.
Maybe he thinks he can manage all these sites from one admin backend?
Maybe he assumes that the modules are only loaded once into server memory?
There are many misconceptions; you need to find out which he has.
At a total guess, I'm inclined to assume that your friend wants to have hundreds of
websites whereby, once a user has joined just one of them, they can freely log into
all the others in the 'community' without registering or having multiple user profiles.
Thanks -Anti-, I will find
Thanks -Anti-, I will find out from him what his particular requirements are.