h2c benchmarks with same Ubuntu tune as before

h2load -n 10 -c 1000 -m 100 http://localhost/perl-script/enquiry.pl starting benchmark... spawning thread #0: 1000 total client(s). 10 total requests Application protocol: h2c progress: 10% done progress: 20% done progress: 30% done progress: 40% done progress: 50% done progress: 6

Re: sealed.pm v4.0.0 is out

Forgive me for the pent up frustration of having our wonderful mod_perl project being completely ignored and abandoned by the Perl Steering Committee's frivolous lingustic interests over the years since the Parrot announcement. SaywerX gave us a reason to be hopeful again. Let's see what they do w

Re: sealed.pm v4.0.0 is out

If the Perl steering committee had any brains left it would have capitalized on the perl 5.34 release and Co announced modperl2 ithread compatibility now available with Perl7’s new release. Instead they are going to kick the tires on the defaults for strictures and warnings until nobody cares a

Re: sealed.pm v4.0.0 is out

The only reason I’ve been vacillating about glibc/malloc thread safety is because I couldn’t fathom the fact that people still believed modperl isn’t compatible with mpm_event at this point in the Perl7 storyline. The old segfaults of the past that happened in glibc malloc were because Perl was

Re: sealed.pm v4.0.0 is out

Religiously avoid setting up per request ithread environment variables. Just use PerlSetEnv in your Webserver config. Everything we did in modperl to support CGI scripts is a train wreck. Get Outlook for iOS From: Joe Schaefer Sent: Monday

Re: sealed.pm v4.0.0 is out

Look into reducing the scope of your interpreters down from the request level to the handler level. If all you are doing is running registry scripts, you will get even better scaling out of just a few ithreads per worker process. Get Outlook for iOS __

Re: sealed.pm v4.0.0 is out

The only impact to your work with modperl is that you will need to assess the ithread-safety of your dependent XS-based modules. For example, use a JSON::XS thread safe alternative- there are several. Get Outlook for iOS From: Joe Schaefer

Re: sealed.pm v4.0.0 is out

There is a mountain of awful advice floating around about ithreads, including pretty much everything going on in Raku around adopting the node.js model instead. It is safe to ignore all that now that SawyerX spit polished all of the perl5 internals. Get Outlook for iOS __

Re: sealed.pm v4.0.0 is out

Many of the performance hacks we’ve encouraged over the years, eg around HTTPD’s lingering close effect, are obsoleted with ithreads. Unless you send flush buckets down the output filter stack yourself, the “response handler” phase exits long before the “connection handler” starts making non bl