Re: Apache + mod_php performance

In article <66fb3d25$0$717$14726298@news.sunsite.dk>,
Arne Vajhøj  <arne@vajhoej.dk> wrote:

On 9/30/2024 8:50 AM, Dan Cross wrote:

In article <vdbq08$1pg2p$2@dont-email.me>,
Arne Vajhøj  <arne@vajhoej.dk> wrote:

On 9/27/2024 8:38 PM, Dan Cross wrote:

In article <vd7hbi$tgu3$2@dont-email.me>,
Arne Vajhøj  <arne@vajhoej.dk> wrote:

And note that keep alive was not needed for me, but it is needed in many
other scenarios:
- web pages with lots of graphics
- high volume server to server web services

>
Actually, it's useful for any scenario in which you may send
several requests to the same server at roughly the same time,
such as an HTML document and separate CSS stylesheet, not just
graphics or "server to server web services".

>
There is no difference in how graphics and CSS are handled,
so the benefits of reusing a connection is the same.
>
But there is a difference in number of requests. CSS will typical
be cached by the browser. So number of CSS requests will be a fraction
of number of HTML requests, while pages with lots of graphics
will have many graphics requests per HTML request.

 
Why do you assume CSS will be cached and graphics will not?

>
Different usage patterns.
>
CSS and JS libraries are usually identical among all
pages at site or a section of a site (to give an identical
look and feel and to make development easier).
>
The graphics (photo, drawings or whatever) on a graphics heavy
page is usually unique for the page.

You have an awful lot of assumptions doing a lot of heavy
lifting for you there, all to justify avoiding using a default
feature of the protocol.  Sorry, I don't find that convincing.

Users usually view several pages at a site or a section of
a site in a session.
>
So when the browser reach a page, then it is very likely that
the CSS and JS are in the cache because they were fetched for
a previous viewed page while it is unlikely that the graphics
is in the cache.

I don't think this reflects how modern web apps are actually
authored.

- Dan C.