[erlang-questions] Using the OTP 'rpc' service (rex) under high load, was: Re: Load balancing/multiplexing rpc calls amongst Erlang Nodes

[Joshua Muzaaya]

indeed, this so helpful of you. You have saved me alot of problems. I was
experiencing the same and thought that i was doing things the wrong way.
Thank you so much.

  <http://www.linkedin.com/pub/muzaaya-joshua/39/2ba/202>
Designed with WiseStamp -
<http://r1.wisestamp.com/r/landing?u=cf16262215eb8784&v=3.11.21&t=1351059836769&promo=10&dest=http%3A%2F%2Fwww.wisestamp.com%2Femail-install%3Futm_source%3Dextension%26utm_medium%3Demail%26utm_campaign%3Dpromo_10>Get
yours<http://r1.wisestamp.com/r/landing?u=cf16262215eb8784&v=3.11.21&t=1351059836769&promo=10&dest=http%3A%2F%2Fwww.wisestamp.com%2Femail-install%3Futm_source%3Dextension%26utm_medium%3Demail%26utm_campaign%3Dpromo_10>



On Wed, Oct 24, 2012 at 7:33 AM, Scott Lystig Fritchie <
fritchie@REDACTED> wrote:

> Hi, Joshua.  One note of caution about the rpc service, or more
> specifically about the 'rex' gen_server that implements the server side
> of the client/server remote execution service.
>
> The 'rex' process is a single OTP gen_server and thus can use at most a
> single CPU core's worth of computation resource.  Experience with using
> rpc/rex with Riak has shown that certain workloads can easily overwhelm
> the rex server's ability to quickly execute requests from remote
> clients.  When possible, I'd recommend avoiding using the 'rpc' module
> and bypass 'rex' by spawn()/spawn_monitor()/spawn_link()'ing worker
> processes directly on a remote node.
>
> -Scott
>



-- 
*Muzaaya Joshua
Systems Engineer
+256774115170*
*"Through it all, i have learned to trust in Jesus. To depend upon His Word"
*
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://erlang.org/pipermail/erlang-questions/attachments/20121024/bd97b0bb/attachment.htm>