[erlang-questions] understanding the scaleability limits of erlang and mnesia

[Brian Acton]

I understand that inserts would take longer in the former example than in
the latter. However, I don't understand why this would so greatly impact
restart / recovery time ? Is this because mnesia is effectively reinserting
the records, rather than blatting the file from another node over the wire ?
Presumably, the latter would be much much faster...

Any references (besides what is on erlang.org) that you use that details
this info ?

Also, rewriting my app to lessen the uniqueness of the indexes is virtually
impossible. I'm dealing with user ids which are inherently unique.

--b


On Tue, Jan 26, 2010 at 12:50 PM, Paul Fisher <pfisher@REDACTED>wrote:

> On Tue, 2010-01-26 at 14:19 -0600, Brian Acton wrote:
> > Can you explain more about how index uniqueness affects recover /
> > startup times ?
>
> Fundamentally, this comes down to the way that ets tables work... Try to
> insert 100000 records with unique index values into a table, then try to
> do 100000 records with either the atoms 'true' or 'false'.  You will see
> the problem in the runtime results.
>
> --
> paul
>
>