[erlang-questions] How to speed up mnesia startup?
Fri Apr 13 00:31:55 CEST 2012
On 12/04/2012, at 9:26 PM, Ulf Wiger wrote:
> Hmm, the first thing that stands out is the inordinate number of tables.
> Out of curiosity, I tried figuring out what is considered a reasonable number of tables for other database management systems:
> - Oracle: over 10,000 tables considered insane
That page has no claim that *Oracle* cannot handle it.
The arguments given are
- that it seems extremely unlikely that people could "design,
implement, or maintain" a system with 10,000 distinct tables
Of course it does not follow that a team could not design,
implement, and maintain an ALGEBRA by means of which 10,000
relation values could be constructed and queried.
- the specific problem looked as if it would fit a two table
That does not mean the OP's problem would suit such a design,
although it well might.
- "flooding the shared pool with 100's of thousands of SQL statements
for one, that would be the first one - doesn't scale very well at all."
This doesn't apply to Erlang/Mnesia.
- You'd have to use dynamic SQL rather than stored procedures in SQL.
This doesn't apply to Erlang/Mnesia either.
> - Postgres: 10,000 tables works fine; practical limit (on ext3) probably 32k
That page actually talks about 10,000 DATABASES in one cluster.
Since each database had 1-5 tables, the test tried about
30,000 TABLES. The 32k limit applies to databases, not tables.
Somebody called "Michael" commented that they had 20,000 tables
in a single database and someone called "wstrzalka" claimed to
have a "similar installation".
> - MySQL Server: no apparent problems
The page asks about (Microsoft) "SQL Server" and also about "MySQL".
"Andy Ansryan" said "I have had a database with 2 million tables"
with "no performance hit at all". As far as I can see all the
answers were about Microsoft SQL Server, not about MySQL.
For what it's worth,
says that the maximum number of tables in Firebird is 32k.
>> Here is my conditions:
>> - DB exists local
>> - more than 60000 tables
>> - sum size is about 28 Giga Bytes.
>> - most tables created options with record_name, attributes(and record_info()) and disc_only_copies.
60,000 tables is, for example, more than Firebird can handle.
The average table size is only 500 kB.
How big are the tuples? How many tuples per table?
I'm pretty sure that there is some structure in the problem domain
that's not being exploited here.
More information about the erlang-questions