On Wed, Oct 24, 2012 at 9:59 AM, Bill Moseley <mose...@hank.org> wrote: > > > On Wed, Oct 24, 2012 at 5:44 AM, Lorn <l...@lornlab.org> wrote: >> >> I'm not following the thread but, did you guys know about >> http://wiki.nginx.org/HttpUploadProgressModule. ? > > > PerlBal (as in this old post: > http://lists.danga.com/pipermail/perlbal/2005-November/000138.html ) can do > this as well.
I can vouch for the scalability of the Perlbal upload tracker. I used it on taperfriendlymusic.org in front of a slashcode based mod_perl app in 2006, and one box was able to handle 50 megabits of uploads with around 10% cpu usage. > > I wonder about the topology. We used to run with Perlbal (and heartbeat > and IP failover) in front of a pool of web servers. We now run with > hardware load balancers in front of a pool of web servers. > > The load balancer does make it easy to adjust the pool -- as well as > gracefully handle a web server dropping out of the pool. I don't want to > add yet another set of servers for an extra proxy layer. > > So, I'm currently thinking of running Nginx on each web server. (Keep-alive > between the load balancer and Nginx, and no keep-alive between Nginx and > Catalyst with maybe Starman.) > > Anyone see why this might be a bad (or good) approach? > > -- > Bill Moseley > mose...@hank.org > > _______________________________________________ > List: Catalyst@lists.scsys.co.uk > Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst > Searchable archive: http://www.mail-archive.com/catalyst@lists.scsys.co.uk/ > Dev site: http://dev.catalyst.perl.org/ > _______________________________________________ List: Catalyst@lists.scsys.co.uk Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst Searchable archive: http://www.mail-archive.com/catalyst@lists.scsys.co.uk/ Dev site: http://dev.catalyst.perl.org/