Worker count when using rackup?

[tomas]

Hi, great work with agoo!

I'm trying to fire the server through rackup (using a regular config.ru) but I'm not sure how to set the number of workers. I tried putting something like this on the config.ru file itself:

Agoo::Server.init(6471, 'root', thread_count: 8, worker_count: 4)

But no workie. How do I accomplish this?

[ohler55]

Use the rackup option -O NAME[=VALUE]. So for a worker count of 2 you would do something like this:

$ rackup -r agoo -s agoo -O wc=2

[tomas]

Gotcha. And thanks for the quick response!

By the way, I forked your repo to fix a few compilation issues. If you're interested I can submit a PR.

[ohler55]

By all means. I use a C11 compiler so miss some of those. If you have them covered a fix would be really helpful.

[tomas]

Great! Will do.

By the way, does agoo support a) listening on a unix socket, and b) hot restarts? (Via USR2 or some other method)

[ohler55]

It does support unix sockets. Checkout the bind_test.rb file.

Agoo does not support hot restarts today. On the plus side it starts pretty fast. :-)

[tomas]

I see. So unix socket not possible via rackup, right? (Couldn't find anything related to it on the rack handler definition)

[ohler55]

Good point. I can add that. If you want to open an issue for that I'll use that for the addition.

I'm curious, rackup introduces a lot over overhead. What are your reasons for using it?

[tomas]

I actually don't use the rackup command regularly. I've always just fired puma or unicorn directly, and have them read the config.ru file and start serving. The only reason I'm using it now is because I'm testing agoo in some of my apps, and want to be able to swap one for another without too much fuss.

I'm not sure what your reasons are not to do it that way, but I think supporting config.ru from the agoo command might make adoption easier.

[ohler55]

I suppose Agoo could look at the file suffix and if a .ru it could assume it is rack. That would be easy enough.

[tomas]

;)

[ohler55]

Created issue #50 and #51.

[ohler55]

I'll put something up for both those issues in the next few days. You comments would be appreciated.