Fragmented tables in Mnesia

[Erlang Questions]

Hi, everyone.

Does someone know if it implies lose of performance using mnesia:activity to execute reads and writes in a fragmented table?

My question goes to indiscriminately use mnesia:activity even in those cases where the table is not fragmanted (yet).
This way, the final user could make its own fragmentations whenever he wants without having to change any code line.
It will be a good option if there is no significative overhead in using such function.

Or maybe there is some other way to prevent code of writting or reading from a table that could be fragmented in the future.
I am new in the "Mnesia Table Fragmenters Club" and my experience is based on the examples found in the documentation.

Thanks in advance, Carlos.-
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://erlang.org/pipermail/erlang-questions/attachments/20030709/e9027d92/attachment.htm>