On Fri, Nov 23, 2018 at 5:44 PM George Neuner wrote:
> Multiple (identical) server instances running on the same machine can
> listen for connections on the same network port - an incoming client call
> will be connected to only one of them. You only need to use different
> ports when services
I probably wasn't very clear about what's going on with Unicorn when I
deploy a new version of the app. It's actually quite simple, and doesn't
require loading new code on the fly. Here's what I do:
1) I update the app server code via: git pull (this doesn't affect the
running processes due
Hi Brian,
On 23 Nov 2018, at 21:46, Brian Adkins wrote:
I'm porting a web application from Ruby/Rails to Racket, and I'd like
something to manage the Racket server processes.
In the Ruby world, I'm currently using Unicorn (
https://en.wikipedia.org/wiki/Unicorn_(web_server) ) prior to that I
I'm glad to hear about the Racket web server's reliability! I'm still
working through the high level architecture, but it seems like one Racket
instance per core make sense to maximize cpu utilization, and then I may
spin up a thread per request w/in each process to maximize memory
4 matches
Mail list logo
