Have you tried just starting more than one? For us we just launch
multiple using proclaunch. Each reads the route configuration from
mongrel's sqlite and connects to appropiate 0MQ port.
-Rob
On 6/18/12 11:09 AM, cd rubin wrote:
Thanks Rob
What I am really trying to work out is that last bit you mentioned -
how exactly to have multiple tir handlers startup and have them all
subscribe to the _same_ mongrel2 socket... For example, I have a tir
hander for the /download path and I would like to launch 5 tir
handlers (and corresponding processes) for it if possible. Green
question I know but I have not found a simple way to do it yet. Thanks
again!
- Daniel
On Mon, Jun 18, 2012 at 1:35 PM, Rob LaRubbio <[email protected]
<mailto:[email protected]>> wrote:
Daniel,
We do this with our handlers. Internally mongrel sets up a
push/pull
socket for sending messages to handlers so 0MQ will round robin across
all of them. It is important to note that the messages are sent
immediately to the handlers instead of the handlers requesting a new
message when they finish with one. This will result in messages
queing
up in a particular handler if there is one slow message in the group.
I don't think there is any special config you need to do, just
starting
multiple tir handlers should get them all subscribing. If you have
issues just post and I'll try to help you out.
-Rob
On 6/17/12 3:25 AM, cd rubin wrote:
>
> Morning all
>
> I have happily succeeded in seeing mongrel2 and tir serve some
dynamic
> content. I now would like to work on some of the performance/process
> tuning that I have imagined possible. My naive hope is that I
can get
> tir to launch more than one process for a particular handler.
With the
> aim being that more than one long-running request can be handled
at a
> time. Where should I be looking to achieve this? Thanks!
>
> - Daniel
