<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<body bgcolor="#ffffff" text="#000000">
We have done again few test, and find that if we shall do transaction
writing, memory usage will grow.<br>
If we will use dirty commands, then memory growing, but not so fast,
and sometimes (and it's interesting fact) even did not grow at all.<br>
Ok, even if we use transactions to operate with Mnesia for about 500
000 times, and Mnesia accumulate 40-60 megabytes, after a few minutes
of idle (beam process is idle - nothing to do to him), memory usage
will fall to 9-11 megabytes. And this gives me opinion to think that
Mnesia under heavy load just delay "free memory" procedure until
"better time" comes. And then this time is come - memory usage very
Is my assumption right ?<br>
Dmitriy Gorbenko wrote:
<blockquote cite="mid:47666E1A.firstname.lastname@example.org" type="cite">
<pre wrap="">Hi all.
Well, I have two .erl files, which makes Mnesia allocating a lot of
memory and vary fast.
What they are doing ? First file wrote to Mnesia table some values, and
then into loop tries to read this value.
Second file only writes to mnesia table in loop, and nothing else.
You can find in this two test ties to use flags like "fullsweep_after",
but they also did not help - memory continue constantly growing.
So, If anyone knows why those test produces so much memory usage, please
- reply me.
Inside the files, you can find small readme, how to run them.
<pre wrap=""><pre wrap=""><pre wrap=""><hr size="4" width="90%">
erlang-questions mailing list