[erlang-questions] Setting maximum amount of data allocated by an Erlang node.‏

[Kannan]

What is the use case? Why are you looking at limiting it in the first
place? May be, you are trying to cure the symptom than the root cause.

Theepan

On Sat, Sep 5, 2015 at 7:14 AM, Zulfiqer Sekender <msekender@REDACTED>
wrote:

> Thanks for the reply. Can't we do anything from Erlang level?
> Thanks.
>
> ------------------------------
> Date: Sat, 5 Sep 2015 05:45:01 +0530
> From: vasdeveloper@REDACTED
> To: achowdhury918@REDACTED
> CC: erlang-questions@REDACTED
> Subject: Re: [erlang-questions] Setting maximum amount of data allocated
> by an Erlang node.‏
>
>
> Please look at OS level configurations. If you are using Linux or Unix
> system, check ULIMIT command.
>
> Theepan
>
> On Sat, Sep 5, 2015 at 5:23 AM, Akash Chowdhury <achowdhury918@REDACTED>
> wrote:
>
> Hi,
>
> I would like to set a number for
>
> a)      simultaneously alive maximum Erlang processes in an Erlang node
>  and
>
> b)      for maximum amount of data allocated by an Erlang node
>
> I know that for process, I have to use the *+P
> <http://www.erlang.org/doc/man/erl.html#max_processes>* command-line
> flag. But what I have to do for setting maximum amount of data allocated by
> an Erlang node.
>
> I looked at the following documentation:
>
> http://www.erlang.org/doc/efficiency_guide/advanced.html
>
> It says setting maximum amount of data allocated by an Erlang node is
> possible, but it doesn’t say how.
>
> Any help will be highly appreciated.
>
> Thanks.
>
> -
>
> Akash
>
> _______________________________________________
> erlang-questions mailing list
> erlang-questions@REDACTED
> http://erlang.org/mailman/listinfo/erlang-questions
>
>
>
> _______________________________________________ erlang-questions mailing
> list erlang-questions@REDACTED
> http://erlang.org/mailman/listinfo/erlang-questions
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://erlang.org/pipermail/erlang-questions/attachments/20150905/dcf9a1be/attachment.htm>