[Typo3-typo3org] Hosting the TYPO3 sites

Sven Wilhelm wilhelm at icecrash.com
Fri Apr 8 21:20:18 CEST 2005

>    a) - short term:
>           - refactor the current TER to be file based
>           - disable other features on TYPO3.org which cause much load
>           - upgrade to 3.8.0 and use caching headers / reverse proxy
what about postgres for an at least short term solution?
If one thing should be clear, then that there is a permanent overhead by
using mysql that is called 'parsing the sql query inside mysql', or I
don't know anything how a database server works.
In any FULL relational database server there is a often a feature called
stored procedures which are predefined sql statements that are optimized
for internal usage. No on request parsing of sql statements, just
execute. Views another nice feature of FULL RDBMS has also this
advantage. Perhaps some possibilities for other optimizations?

Next questions because no one answers on that. If you try to serve
highloaded sites, do you services this sites with standard distribution
packages or with optimized ones. The whole discussion in the last weeks
lacks on clear facts. Everyone discusses, no one or only a few people no
the something. If external people try to help they can't help because of
this. Other statements heard in past, "the target people know the
facts", ok.
As a youngster (not in sysadmin mind, but in the typo3-network) I'm
quiet now.


More information about the TYPO3-team-typo3org mailing list