[prev in list] [next in list] [prev in thread] [next in thread] 

List:       apache-modperl
Subject:    Re: Moving away from pure application server tiers
From:       Joe Schaefer <joe () sunstarsys ! com>
Date:       2022-08-28 15:16:04
Message-ID: CAFQGv+asemRAaoCcaGK4icxJKimiv73K4YrY-x7Xm94hsUphrQ () mail ! gmail ! com
[Download RAW message or body]

I don't preload any Perl Modules at server startup and don't recommend you
do either, if you want new ithread cloning (of the parent) to be quick.
The only legitimate knock on ithreads is the spinup lag, but that is
completely mitigated by mod_perl's ithread pool mgmt, which is exactly the
same (caching) model as prefork when UNIX fork() was slow (1990s).

On Sun, Aug 28, 2022 at 11:03 AM <joe@sunstarsys.com> wrote:

> There is an emerging industry trend towards consolidation an integration
> of webstack technology, and mod_perl + mpm_event is well-positioned to eat
> everyone else's lunch in this space.  The only real reason fastcgi-like
> frameworks won out over the past two decades is because threading was/is
> crap in Dynamic Programming Languages.  Nobody could successfully embed
> into a threaded webserver, so they went around celebrating multi-tiered
> architectures instead.
>
>
>
> As the posted benchmark shows, you don't need a massive investment in a
> cluster of horizontally scalable docker containers to service your dynamic
> content load.  Instead, you need to horizontally scale your modestly sized
> front-end apache servers running mpm_event+mod_perl with a Network
> (TCP-level) Load Balancer in the front.
>


-- 
Joe Schaefer, Ph.D.
We only build what you need built.
<joe@sunstarsys.com>
954.253.3732 <//954.253.3732>

[Attachment #3 (text/html)]

<div dir="ltr">I don&#39;t preload any Perl Modules at server startup and don&#39;t \
recommend you do either, if you want new ithread cloning (of the parent) to be quick. \
The only legitimate knock on ithreads is the spinup lag, but that is completely \
mitigated by mod_perl&#39;s ithread pool mgmt, which is exactly the same (caching) \
model as prefork when UNIX fork() was slow (1990s).  </div><br><div \
class="gmail_quote"><div dir="ltr" class="gmail_attr">On Sun, Aug 28, 2022 at 11:03 \
AM &lt;<a href="mailto:joe@sunstarsys.com">joe@sunstarsys.com</a>&gt; \
wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px \
0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div \
class="gmail-msg-6525115895187006115"><div lang="EN-US" style="overflow-wrap: \
break-word;"><div class="gmail-m_-6525115895187006115WordSection1"><p \
class="MsoNormal">There is an emerging industry trend towards consolidation an \
integration of webstack technology, and mod_perl + mpm_event is well-positioned to \
eat everyone else's lunch in this space.   The only real reason fastcgi-like \
frameworks won out over the past two decades is because threading was/is crap in \
Dynamic Programming Languages.   Nobody could successfully embed into a threaded \
webserver, so they went around celebrating multi-tiered architectures \
instead.<u></u><u></u></p><p class="MsoNormal"><u></u>  <u></u></p><p \
class="MsoNormal">As the posted benchmark shows, you don't need a massive investment \
in a cluster of horizontally scalable docker containers to service your dynamic \
content load.   Instead, you need to horizontally scale your modestly sized front-end \
apache servers running mpm_event+mod_perl with a Network (TCP-level) Load Balancer in \
the front.<u></u><u></u></p></div></div> </div></blockquote></div><br \
clear="all"><div><br></div>-- <br><div dir="ltr" class="gmail_signature"><div \
dir="ltr">Joe Schaefer, Ph.D.<div><img width="96" height="26" \
src="https://ci3.googleusercontent.com/mail-sig/AIorK4xJ9wGYA7VWN-zW0DcpKll4IC6JxLGTMmDkmdn4h4eHliQhOGGu1nAHJcSkYVnw1jXF8E--UGA"></div><div>We \
only build what you need built.</div><div><div><div>&lt;<a \
href="mailto:joe@sunstarsys.com" \
target="_blank">joe@sunstarsys.com</a>&gt;</div><div><a href="tel://954.253.3732" \
target="_blank">954.253.3732</a></div><div><br></div><div><br></div></div></div></div></div>




[prev in list] [next in list] [prev in thread] [next in thread]