mnesia usage optimisation
Thu Jul 25 23:36:25 CEST 2002
But given that Luke's code runs as part of a transaction, he can't create a
table from within a transaction. If you can get away from being in a
transaction, you can probably use the mnesia:ets function...
From: Sean Hinde [mailto:]
Sent: 25 July 2002 21:17
To: 'Luke Gorrie'
Subject: RE: mnesia usage optimisation
I think the problem is that indexes are built using a linear search
mechanism when you have many items with the same value.
You could get around this by creating a new table wherever you wish to store
more than 1 destination node against a single source node - store the name
of the new table against your source node instead of the actual
destinations, and store all the destinations in the new table.
NOTICE AND DISCLAIMER:
This email (including attachments) is confidential. If you have received
this email in error please notify the sender immediately and delete this
email from your system without copying or disseminating it or placing any
reliance upon its contents. We cannot accept liability for any breaches of
confidence arising through use of email. Any opinions expressed in this
email (including attachments) are those of the author and do not necessarily
reflect our opinions. We will not accept responsibility for any commitments
made by our employees outside the scope of our business. We do not warrant
the accuracy or completeness of such information.
More information about the erlang-questions