Hi David, Here’s a link to the files I use to start a Dancer2 app on RedHat: rcfile: https://github.com/Q-Technologies/fcollect/blob/master/packaging/fcollect_rc... <https://github.com/Q-Technologies/fcollect/blob/master/packaging/fcollect_rcfile> it’s config: https://github.com/Q-Technologies/fcollect/blob/master/packaging/fcollect_sy... <https://github.com/Q-Technologies/fcollect/blob/master/packaging/fcollect_sysconfig.example> (these are used for including in an RPM so have different names to when they are deployed) Basically Starman runs as many workers as specified in the config file - each worker is a process - not a thread as such. I have one app which has 16 workers - it manages hundreds of simultaneous connections quite comfortably. Cheers, Matt
On 3 Nov 2015, at 4:02 pm, David H <untg99@gmail.com> wrote:
Hi All,
I just need some basic advice on deploying Dancer2 onto RedHat. I am wanting to deploy it to be multithreaded, or at least not to block when it is running requests.
Starman and Twiggy both seem to not want to run multithreads for some reason and I tried the Apache way and it just seems to compile the code everytime which ended up being not any faster than a single thread.
What ways do people here deploy the app to be fast/multi-threaded?
I tried this:
http://search.cpan.org/dist/Dancer/lib/Dancer/Deployment.pod#Running_as_a_cg... <http://search.cpan.org/dist/Dancer/lib/Dancer/Deployment.pod#Running_as_a_cgi-script_%28or_fast-cgi%29_under_Apache>
However it seemed to recompile everything for every request.
I understand about static files being hosted in front etc...as well, which I may do in the future.
Thanks,
David _______________________________________________ dancer-users mailing list dancer-users@dancer.pm http://lists.preshweb.co.uk/mailman/listinfo/dancer-users