Download as ODP, PPTX
Choosing a Web Architecture for Perl
- 1. Choosing a WebArchitecture for Perl Perrin Harkins We Also Walk Dogs
- 2. This used tobe an easy decision Netscape, or Apache for you hippies
- 3. CGI, or NSAPIif you enjoy core dumps
- 4. Server-side development matured,and it stayed easy Apache became the standard web server
- 5. mod_perl became theway to run Perl
- 6. FastCGI was lookingpeaky Outside of Amazon's reality distortion field anyway
- 7. Then two thingshappened Ruby came along Renewed interest in FastCGI
- 8. Thanks, Ruby! Non-blockingI/O became fashionable Memcached
- 9.
- 10.
- 11. Now we havemany choices Web servers Apache
- 12.
- 13.
- 14.
- 15.
- 16.
- 17.
- 18.
- 19. FastCGI Many implementationsfor different servers
- 20. Daemons are managedby the web server or an external process
- 21. Has hooks forauth, logging, and filtering, but not always implemented and rarely used
- 22. HTTP Reverse proxyforwards HTTP requests to apache/mod_perl backend
- 23.
- 24. Stealing good ideasfrom Python
- 25. Simpler than FastCGI,so theoretically could be faster
- 26. The graveyard ofalternative Perl daemons SpeedyCGI
- 27.
- 28. Both replace the#! line and daemonize your program
- 29. Biases Long-time mod_perlcontributor
- 30. Member of ApacheSoftware Foundation Don't believe a word I say!
- 31. Apache 2.2 mod_proxy+ mod_perl Frontend apache runs threaded worker MPM
- 32. Backend apache runsprefork MPM
- 33. All popular apachemodules (mod_ssl, mod_rewrite, mod_security, mod_deflate, caching, auth) are available
- 34. mod_proxy_balancer provides loadbalancing
- 35. Apache 2.2 mod_fastcgiFrontend runs threaded worker MPM
- 36. As with mod_proxy,all popular apache modules are available
- 37. Three poorly-named configurations:”Static” starts a set number of procs at server startup
- 38. ”Dynamic” starts anew proc every time it gets a request up to a configured limit
- 39. ”Standalone” sends requeststo daemon you start
- 40. Apache 2.2 mod_fastcgiCan run separate versions of same package name in separate daemons True for mod_perl too if you run multiple backends, but less obvious Seamless restart for code upgrades in standalone mode Start a new set of procs on same socket and shut down the old ones
- 41. Could get closewith two mod_perl backends, but not simple
- 42. Lighttpd mod_fastcgi Non-blockingI/O server
- 43. Supports static andstandalone FastCGI
- 44.
- 45. Solid selection ofmodules with equivalents of most popular apache ones
- 46. Same restart advantagesas FastCGI on Apache
- 47. Load balancing acrossFastCGI daemons
- 48. Lighttpd mod_scgi SameLighttpd, different protocol
- 49.
- 50. nginx FastCGI Anothernon-blocking I/O server
- 51.
- 52. Does not supportAuthorizer role
- 53.
- 54.
- 55. nginx proxy +mod_perl Load balancing
- 56. What about runningnaked mod_perl? Static requests
- 57. Buffering for slowclients
- 58.
- 59. Benchmark methodology Verysimple Catalyst app Sleeps for 0.1 seconds
- 60. Returns 35K ofHTML (perl.com homepage) Brief run of ab (Apache Bench) with intended concurrency to warm up server
- 61. ab tests atconcurrency of 10, 50, 150, 200
- 62. General findings FastCGIstatic mode is difficult to use with apache/mod_fastcgi Trial and error to find magic number
- 63. Worked better withLighttpd FastCGI standalone mode is unusable on Lighttpd Load balancing feature marks daemons as down if they're too busy to answer right away and rejects requests SCGI Perl implementations incomplete
- 64.
- 65. Not really applesto apples mod_perl does other things
- 66. Filters on non-perlcontent (PHP, etc.)
- 67. Customize server andrequest phases
- 68. Replace HTTP withyour own protocol Apache 2 + mod_perl 2 is a server kit
- 69. Thanks! And pleasehelp me add more servers...