[erlang-questions] "been there done that"

Jesper Louis Andersen jesper.louis.andersen@REDACTED
Wed Mar 12 10:06:55 CET 2014

Many of the Erlang web servers will reuse a process for the next request
and only cycle them once in a  while. And they will systematically extend
number of processes that are sitting and waiting. This avoids spawning a
new process on each request, but still allows the system to grow in
capacity should it be needed.

The rule of thumb is: Make a new process per request. If this seems to be a
bad idea, then measure and change the scheme. The problem is that these
more intricate process schemes take more code and are more error prone. So
if you can avoid it, you can have better code. Measurement is key!

On Wed, Mar 12, 2014 at 12:00 AM, Raoul Duke <raould@REDACTED> wrote:

> in
> https://erlangcentral.org/catch-me-if-you-can-processing-terabytes-in-secs
> there's an off hand comment about not going overboard, like spawning a
> new process for every request. i'd love to hear more about such
> pragmatism. please, people speak up with rules of thumb, and
> dos-and-don'ts.
> thanks.
> _______________________________________________
> 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/20140312/da43f039/attachment.htm>

More information about the erlang-questions mailing list