Would be very interested in the recipe please. We are well under way with a major development on starman, but have not tested under load yet - so you email caused me concern. Any other opinions on the views presented by Hermann?
Z > -----Original Message----- > From: dancer-users [mailto:[email protected]] On Behalf Of > Hermann Calabria > Sent: 24 November 2015 21:03 > To: Perl Dancer users mailing list <[email protected]> > Subject: Re: [dancer-users] Dancer2 deployment > > At iVouch, we used Starman for several months, but ran into problems with > processes that wouldn't terminate gracefully and pile on top of each other, > causing eventual memory overruns. I know many folks here recommend > Starman, but in a heavy production environment, Starman caused too many > problems for us. So we switched to uWSGI and haven't looked back since... > uWSGI is an amazing piece of software, and is well-supported and continuously > updated because a lot of Python-based apps use it. It also happens to support > Perl/PSGI applications out of the box, which is what drew us to it. > > https://uwsgi-docs.readthedocs.org/en/latest/ > > On top of uWSGI, we run nginx to offload the static asset load, handle SSL, > resolve redirects, etc. > > The combination is dreamy; we've done extensive load testing and it all works > super well and super fast. It took several weeks to fine-tune everything, > and if > there's interest, I'd be happy to post our "recipe" for deploying D1 on uWSGI > on > nginx. > > -----Original Message----- > From: Warren Young > Sent: Monday, November 23, 2015 6:59 AM > To: Perl Dancer users mailing list > Subject: Re: [dancer-users] Dancer2 deployment > > Having said all of that, I certainly do recommend running your Dancer app > behind some kind of reverse proxy server. That will offload the static asset > load > from Dancer, putting it all on the proxy server. > > That gives you a kind of parallelism all by itself, since the proxy server > will be > fully concurrent: it can serve static assets from other threads/children > while one > of those is blocking on Dancer waiting for a dynamically-generated web page. > Since most web page hits serve many more static assets than dynamic ones, it > is > perfectly sensible for most of the available resources to be taken up by the > proxy server. > > If your web app is so “heavy” that it needs a large fraction of the computer’s > available resources, you’re probably at a scale where you should be offloading > static content onto a CDN. > _______________________________________________ > dancer-users mailing list > [email protected] > http://lists.preshweb.co.uk/mailman/listinfo/dancer-users > > _______________________________________________ > dancer-users mailing list > [email protected] > http://lists.preshweb.co.uk/mailman/listinfo/dancer-users _______________________________________________ dancer-users mailing list [email protected] http://lists.preshweb.co.uk/mailman/listinfo/dancer-users
