I think Perl is fine, but naive Perl (or anything else) doesn’t scale. Are you actually maxing out your CPU (re-examine your code) or are your mod_perl instances all hanging around waiting for a database to return (re-examine your queries/indices).
- Mark > On 28 Jan 2019, at 21:27, John Dunlap <j...@lariat.co> wrote: > > Yes! Lots of traffic is arguably the best kind of problem to have! :) We can > definitely throw servers at the problem and scale horizontally but those > costs add up and I'm afraid that, unless we can somehow get more concurrency > out of mod_perl, a day will come when we're forced to acknowledge that we can > do more work for less money in a different language. I was really hoping that > a different MPM and http/2 would help in that regard but it's not sounding > hopeful. :( > > On Mon, Jan 28, 2019 at 9:18 PM Mark Blackman <m...@blackmans.org > <mailto:m...@blackmans.org>> wrote: > > >> On 28 Jan 2019, at 21:14, John Dunlap <j...@lariat.co >> <mailto:j...@lariat.co>> wrote: >> >> Our servers already have 32 Intel(R) Xeon(R) CPU E5-2620 v4 @ 2.10GHz >> cores(if you count hyper threading) so optimization is the road I've been >> going down. I've also Apache::VMonitor to get, at least, *some* insight into >> the internals of mod_perl but I'm uncertain how to use the information it >> gives me to optimize the server. > > Plenty of traffic sounds like a nice problem to have, more machines then? :) > I have a hosting business (UK) on the side (http://www.exonetric.com > <http://www.exonetric.com/>) and would love to sell you some hosting! On the > other hand, if your Perl just needs some TLC, then plenty of contractors can > help find the hotspots and optimise for you. > > - Mark > > > -- > John Dunlap > CTO | Lariat > > Direct: > j...@lariat.co <mailto:j...@lariat.co> > > Customer Service: > 877.268.6667 <> > supp...@lariat.co <mailto:supp...@lariat.co> > <100x60.png> > <100x60.png>
