Sounds like your idea has validity. It may be worth an experiment - but actually
i think what you would really like to do is build on top of unicorn horn.
I'm a bit curious why you have hundreds of daemons.
That looks interesting. Perhaps I will dig into that sometime.
> I'm a bit curious why you have hundreds of daemons.
I don't have hundreds. I have about 80 but soon may hit a hundred.
They are running on different machines about twenty per machine. How
many I can run is limited by the RAM in the VPS so if I can cut down
on memory usage I can save money by using less servers.
What do the daemons do? - you mention they need the rails environment
- what are they working with?
are they all different environments or the same rails?
They do all kinds of different things. There are also multiple copies
of them running. They all connect to a message queue and pass messages
back and forth asking for work to be done. So there might be 10
workers of one type and three workers of another type depending on the
> are they all different environments or the same rails?
Same rails. They all load the rails environment because they need to
access the models, libs etc of the rails app they are in.
I was thinking of making them not load the rails environment and
instead have them hit the rails server via REST calls but some of the
workers might take a pretty long time. I might still try that approach
but I would have to make sure I have enough concurrency in the rails
app to handle the volume. The volume would be pretty high for sure.