Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
« Groups Home
Erlang Programming
Home
+ new post
About this group
Join this group
Message from discussion gproc scalability, shared ets, links and using terminate/2
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
Joseph Norton  
View profile  
 More options Nov 9 2011, 9:17 am
From: Joseph Norton <nor...@lovely.email.ne.jp>
Date: Wed, 9 Nov 2011 23:17:02 +0900
Local: Wed, Nov 9 2011 9:17 am
Subject: Re: [erlang-questions] gproc scalability, shared ets, links and using terminate/2
Print | View thread | Show original | Report this message | Find messages by this author

I've been using a "goodbye" patch for the gproc application to help move some of the cleanup work to the client side and lessen the work of the centralized gproc server.

https://github.com/norton/gproc/commit/e2c4108c2ceae5d86ca78f9f1d5e5c...

Not (quite) sure if this is helpful to your use case or not.

- Joe N.

On Nov 9, 2011, at 11:00 PM, Max Lapshin wrote:

> On Wed, Nov 9, 2011 at 1:06 PM, Ulf Wiger
> <ulf.wi...@erlang-solutions.com> wrote:

>> It's true that link/1 has that advantage.

>> The disadvantage is that if the server crashes, and is linked to, say, 100K processes, the EXIT signal will be duplicated that many times, likely forcing an OOM crash.

> I understand. But I don't have anything to do, except hoping that
> server will not crash, because with monitor in my situation system
> gets frozen under normal load.

> And 100 K of messages is not a reason for OOM. Dumping these messages
> will be an OOM, error logger is the main reason to bring down VM.

> By the way, have you seen my previous claim about non-atomic process startup?
> Using supervisor  {error, {already_started,Pid}} feature is also not
> 100% unreliable because of race condition.
> _______________________________________________
> erlang-questions mailing list
> erlang-questi...@erlang.org
> http://erlang.org/mailman/listinfo/erlang-questions

_______________________________________________
erlang-questions mailing list
erlang-questi...@erlang.org
http://erlang.org/mailman/listinfo/erlang-questions

 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Create a group - Google Groups - Google Home - Terms of Service - Privacy Policy
©2013 Google