[TYPO3-project-4-3] Is it time to ship optimized TYPO3 by default?

[Michael Stucki]

Hi Dmitry,

I remember this.... :-)

> Some time ago I made an attempt to create and have optimal TYPO3
> configuration as TYPO3 default configuration. Unfortunately this was
> turned down [1].
> 
> My idea is simple. Each request to Backend uses huge amount of HTTP
> requests (over 70 according to [2]). By default MSIE is configured
> to have only 2 requests per server at one time. So Backend is slowed
> down for unnecessary reason.
> 
> Fortunately a very simple measure can improve the situation
> dramatically. There are certain _.htaccess files in the core. If
> they are renamed to .htaccess, browsers will cache all CSS, JS and
> static image files for 7 days. This will decrease number of requests
> significally. Anyone can try it and see effects immediately (do not
> try on localhost though, because there is no network delay on
> localhost).

I can confirm this. If you want to test this, I recommend using the
Firefox extension "lori" (life-of-request-info) which displays how many
files were loaded on each request: http://lori.mozdev.org/
Download: https://addons.mozilla.org/de/firefox/addon/1743

> Unfortunately my proposal was turned down because ~some~
> installation can have mod_expires or AllowOverride disabled. Due to
> some these installations the rest of the world gets suboptimal slow
> version of TYPO3 and have no idea that they can have much better
> speed and much less traffic.

Sad but true.

> I propose to reverse the situation. Let the minors care and remove
> .htaccess if they want to have their suboptimal configuration. Let
> the rest of the world enjoy high speed TYPO3.

I would have loved to see an Apache directive that can ignore those
settings if they are not allowed - instead of throwing a server error.
However, there seems to be no interest for such a feature, and
unfortunately it's also not possible for us whether or not the
directives are allowed in this setup.

It seems we have no other way than just doing it and see what breaks. So
yes I now agree with you.

One could say it is the same like having to raise PHPs "memory_limit"
for running TYPO3.

> What needs to be done? Fix [3] and [2], add a line to NEWS.txt about
> it. That's all.

The info in NEWS.txt is a must!

There is still one change which I do not like, though: The protection of
typo3/install/ should stay disabled, as it will fail in every
installation (it points to an inexisting AuthUsers file). Please drop
it, it is not part of the speed optimization anyway.

- michael
-- 
Use a newsreader! Check out
http://typo3.org/community/mailing-lists/use-a-news-reader/