Re: HTTP and MPM support
Mark Blackman <[email protected]>
| Newsgroups | gmane.comp.apache.mod-perl |
|---|---|
| Message-ID | <[email protected]> |
Ok, hopefully Amazon Cloudfront is already using HTTP/2 on your behalf and proxying just the dynamic content requests via HTTP/1.1 to your mod_perl instances. > On 28 Jan 2019, at 21:02, John Dunlap <[email protected]> wrote: > > We can give that a try but I'm not sure how much it would help us because we're already pulling all of our static content directly from Amazon Cloudfront. The vast majority of our requests are for dynamic content. > > On Mon, Jan 28, 2019 at 8:38 PM Mark Blackman <[email protected] <mailto:[email protected]>> wrote: > > Given that Perl is single-threaded by design and history and has no reliable support for threading, I think that mod_perl and direct http/2 support in the same instance are probably fundamentally incompatible. I.e. if you have 10 perl threads running (each in a single process), then it doesn’t matter if you can multiplex 20 http/2 connections, they will all just block. If you’re very attached to mod_perl, you should already be using a 2-tier strategy anyway, with N fat mod_perl Apache instances handling only HTTP/1.1 requests and a second front-end proxy layer of whatever front-end proxy makes sense handling HTTP/2 requests for both static and dynamic content requests. This was standard advice 20 years ago as far as I recall and is even more prudent now. > > - Mark > > > -- > John Dunlap > CTO | Lariat > > Direct: > [email protected] <mailto:[email protected]> > > Customer Service: > 877.268.6667 <> > [email protected] <mailto:[email protected]> > <100x60.png> > <100x60.png>