I'm not sure about this problem but we have had problems with mnesmosyne
queries permanently hanging and causing the system massive load. We have
replaced all occurences with match_object etc until it is sorted out.
I guess the much rumoured ets:select mechanism is what is required to turn
mnemosyne into somethng a little more optimal?
> -----Original Message-----
> From: Hakan Stenholm [mailto:etxhste]
> Sent: 23 March 2001 16:34
> To: erlang-questions
> Subject: Mnemosyne
> Acording to
> http://avweb.etxb.ericsson.se/~etxblau/ErlangCosts.html: >
> "Each mnemosyne query creates a temporary process. In the current
> Mnemosyne implementation the temporary process
> can for complex queries grow very very large, and even force
> the runtime
> system to start swapping memory to disk.
> Therefore, don't use Mnemosyne in cases where you easily can hardcode
> the queries, and if you use Mnemosyne - always
> check that the execution time and memory consumed for complex queries,
> and for serches on large tables, is within reasonable limits."
> this was true in 1997, but is it still true ? - does it still
> use large
> amounts of memory (many other things mentioned on this
> page are no longer relevant) ?
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.