100% cpu with faye-websocket

100% cpu with faye-websocket

[Lion Vollnhals]

Hi,

please CC me as i am not on the list.

i am using rainbows (configured with eventmachine) to serve faye websocket connections.
see https://github.com/faye/faye-websocket-ruby.

when the first user connects (using websocket protocol), cpu usage goes to 100% and stays there.
even when the user is idle or disconnects.

is this normal behavior?

i inspected the process using dtrace under mac os x and saw that the process is doing a lot of read and write system calls all the time.
i can observe the same 100% cpu behavior on linux. so this is not a mac os x issue.

here is my config file and command line:

# rainbows.conf
Rainbows! do
  use :EventMachine
end

rainbows config.ru -c path/to/rainbows.conf -E production -p 9292


regards,
Lion Vollnhals
_______________________________________________
Rainbows! mailing list - rainbows-talk-GrnCvJ7WPxnNLxjTenLetw@public.gmane.org
http://rubyforge.org/mailman/listinfo/rainbows-talk
Do not quote signatures (like this one) or top post when replying

Re: 100% cpu with faye-websocket

[Eric Wong]

Lion Vollnhals <lion.vollnhals-gM/Ye1E23mwN+BqQ9rBEUg@public.gmane.org> wrote:
> Hi,
> 
> please CC me as i am not on the list.
> 
> i am using rainbows (configured with eventmachine) to serve faye websocket connections.
> see https://github.com/faye/faye-websocket-ruby.
> 
> when the first user connects (using websocket protocol), cpu usage goes to 100% and stays there.
> even when the user is idle or disconnects.
> 
> is this normal behavior?

Have you contacted other faye users/developers on this issue?
Hopefully somebody else can help you sooner.

I'm not familiar with faye at all (this is the first I've heard of it,
even), so it'll take me some time to get up to speed.  It's been a
long while since I've looked at websockets, too.
_______________________________________________
Rainbows! mailing list - rainbows-talk-GrnCvJ7WPxnNLxjTenLetw@public.gmane.org
http://rubyforge.org/mailman/listinfo/rainbows-talk
Do not quote signatures (like this one) or top post when replying