Dear Christophe, the number of table and the traffic of your websites are two differents things.
First the number of tables that can be created in a DB and managed by MySQL depends in fact of the operating system and the maximum number of files that can be created on the disk into a same directory. MySQL create 3 files per tables.
So if you have 100 websites that each site contain 50 table, this means that you will have 5000 tables that correspond to 15000 files in the same directory.
If you can create separated DB, you can also use them.
All the architectures are possibles.
Single DB
Two DB (1 master + 1 slave)
As many DB as websites.
Concerning the traffic, the overhead of JMS is very small and everything is pre-computed when the slave site are created.
So JMS itself can be considered as very small.
So the question remain to know the global traffic that a server is able to process.
The result with JMS is more less equal to the number of separated joomla installed on the same server.
If for example you have 50 websites on the SAME server with 50 separated joomla then the workload will be more less the same with JMS and 50 websites using a SINGLE joomla.
The major advantage of JMS is that you have a single joomla to update and maintain when you have bug fixes or security fixes or whatever.
In the case where you have 50 joomla to update the time require is higher.
So with JMS, you benefit of a single maintenance.
|