[TYPO3-Performance] General questions

[Dan Osipov]

Definitely, and that's my point about losing extensibility (backward 
compitability). Unfortunately, v3.0 is no better in that respect.

Unfortunately, it looks like the core is not much better. There is a lot 
of power in Typo3 features, such as localization, extensibility through 
XCLASS and hooks, etc, but this comes at the cost of performance.

Dan Osipov
Calkins Media
http://danosipov.com/blog/

Martin Kutschker wrote:
> I think Ingo refers to the fact that tt_news' code is a but, ah,
> unorganized. It has grown over the years and it's far from what can be
> said to be a beautiful code. Thanx to Kasper and Rupert to have written
> it. It served it's purpose, but it's IMHO a completely lost cause, when
> it comes to have a reasonable structure. It's overburden with backwards
> compatibility even more then the Core. And it has some very strange
> queries to do its job.
> 
> Masi
> 
> Dan Osipov schrieb:
>> I disagree - I think it can be optimized by running fewer queries, but
>> it will lose its extensibility (is that a word?)...
>>
>> Dan Osipov
>> Calkins Media
>> http://danosipov.com/blog/
>>
>> Ingo Renner wrote:
>>> Dmitry Dulepov [typo3] wrote:
>>>
>>>> Ah, well, tt_news is a good example :) If you look also to the
>>>> queries that it makes, you will see that they neither can be
>>>> optimized, nor indexes can be used. It is always filesort + temporary
>>>> table. If those queries are split in 3, they would run much faster
>>>> than that large single query...
>>> I'd say tt_news is a story on its own anyways ;)
>>>
>>>
>>> Ingo
>>>