agoo: fails to launch in clustered mode

Trying to compare performance in our app with puma So far 1 agoo process is slightly slower than our clustered 4 puma processes 3692 req/s vs 4424 req/s

However agoo doesn’t seem to launch in clustered mode. ./bin/agoo -p 8080 -w 4 -t 32

the above doesn’t output any errors, just never gets to the line: listening on http://:8080.

however ./bin/agoo -p 8080 -t 32 does work

We run the app in a docker container: https://github.com/PlaceOS/auth/blob/agoo-server/Dockerfile

Any ideas?

About this issue

Original URL
State: closed
Created 2 years ago
Comments: 17 (10 by maintainers)

Most upvoted comments

Both sound like good ideas. Look for those additions in the near future.

ohler55 on Dec 7, 2023

Hi there! I came across from the web page benchmark page (congrats with being the fastest in ruby). Running the Rails app in clustered mode would require to have at least before_fork hook as normally this is the place to close any connections that would be corrupted in the parent on child process exit. Like that

before_fork do
  Sequel::DATABASES.each(&:disconnect)
end

Also it would be nice to have some kind of an after_worker_fork callback to have the opportunity to do some work in the context of new spawned worker

frvade on Dec 6, 2023

I’ll look into it this weekend. My unit tests worked last time I check so with any luck there is some configuration addition that is needed.

ohler55 on Mar 4, 2022