From: Martin D. <mrt...@gm...> - 2013-04-12 14:38:34
|
Hello, I perform performance tests on our app and I manage to crash the VM every time with the above message. What bothers me is: 1. the allocation request is low: 1-4 MB 2. the total amount of used memory is also low: 300-500 MB (the test machine has 8GB of RAM) 3. all processes have low consumption of memory (highest 3 MB) but the app creates many(?) of them: about 2 500 4. there is no Running process, one is Garbing and it is started by YAWS. About 100 processes are Scheduled and all the rest are Waiting. This state repeats on every run. The test machine is Windows 8, 4 cores, 8 GB Ram, running Erlang R16B and YAWS 1.6. Thank you very much, Martin |
From: Robert R. <rtr...@go...> - 2013-04-12 15:04:17
|
Hi Martin, not sure I'm reading that correctly, but 2500 * ~2 MB is ~5GB. So I don't know how you are measuring 500MB overall usage. Robby On Apr 12, 2013 3:38 PM, "Martin Dimitrov" <mrt...@gm...> wrote: > Hello, > > I perform performance tests on our app and I manage to crash the VM > every time with the above message. What bothers me is: > 1. the allocation request is low: 1-4 MB > 2. the total amount of used memory is also low: 300-500 MB (the test > machine has 8GB of RAM) > 3. all processes have low consumption of memory (highest 3 MB) but the > app creates many(?) of them: about 2 500 > 4. there is no Running process, one is Garbing and it is started by > YAWS. About 100 processes are Scheduled and all the rest are Waiting. > This state repeats on every run. > > The test machine is Windows 8, 4 cores, 8 GB Ram, running Erlang R16B > and YAWS 1.6. > > Thank you very much, > > Martin > _______________________________________________ > erlang-questions mailing list > erl...@er... > http://erlang.org/mailman/listinfo/erlang-questions > |
From: Martin D. <mrt...@gm...> - 2013-04-12 15:12:15
|
The highest amount of memory per process is 3MB. There are only 10-15 of them. The rest have lower amount of used memory. Some - few hundred bytes. The overall usage I see through crashdump_viewer under Memory Information -> Memory. Martin On 4/12/2013 6:04 PM, Robert Raschke wrote: > Hi Martin, > > not sure I'm reading that correctly, but 2500 * ~2 MB is ~5GB. So I don't > know how you are measuring 500MB overall usage. > > Robby > On Apr 12, 2013 3:38 PM, "Martin Dimitrov" <mrt...@gm...> wrote: > >> Hello, >> >> I perform performance tests on our app and I manage to crash the VM >> every time with the above message. What bothers me is: >> 1. the allocation request is low: 1-4 MB >> 2. the total amount of used memory is also low: 300-500 MB (the test >> machine has 8GB of RAM) >> 3. all processes have low consumption of memory (highest 3 MB) but the >> app creates many(?) of them: about 2 500 >> 4. there is no Running process, one is Garbing and it is started by >> YAWS. About 100 processes are Scheduled and all the rest are Waiting. >> This state repeats on every run. >> >> The test machine is Windows 8, 4 cores, 8 GB Ram, running Erlang R16B >> and YAWS 1.6. >> >> Thank you very much, >> >> Martin >> _______________________________________________ >> erlang-questions mailing list >> erl...@er... >> http://erlang.org/mailman/listinfo/erlang-questions >> > |
From: chris h. <bit...@gm...> - 2013-04-14 05:34:44
|
--Chris H -- -- -- Ours is a world of nuclear giants and ethical infants. -- General Omar N. Bradley -- The contest for ages has been to rescue liberty from the grasp of executive power. -- Daniel Webster -- All difficult things have their origin in that which is easy, and great things in that which is small. -- Lao Tzu |