[TYPO3-core] Memory system woes

Bernhard Kraft kraftb at kraftb.at
Thu Feb 14 20:48:31 CET 2013


Am Mon, 11 Feb 2013 00:56:36 +0100 schrieb Christian Kuhn:

> Disclaimer: This does not mean that memory shouldn't be optimised at
> all. If our application does something insane that can be solved more
> elegantly with less memory consumption: Go ahead, we love those patches!

It is a known fact that one can write an algorythm optimized for speed or 
for memory. For example take a calculation of prime numbers:
-------------------
When optimized for speed you would use some sieve algorythm which creates 
an in-memory table (or a file stored on RAM disks) to store already found 
primes and use them to calculate the next ones.

When optimized for memory usages you would simply divide each new number 
x to be tested by every other (non-even) number up to x/2.
-------------------

So there's always a tradeoff between speed and memory. I guess as long as 
PHP is not multitasking and we have CPUs having some kilocores (altough 
simple "microcores" - not as full-featured as an x86 CPU) - which is the 
current situation we should try to optimize on speed.

I guess the site Dmitry mentioned (serving 2000 req/s) is some page 
having lots of FE Users so T3 caching is not an alternative. Of course 
many FE-User related things which dissallow caching can be loaded of to 
the client side (using JS.) But this does not solve the problem of 
calculation power. You simply move the CPU power requirements from the 
server to the customer. Many customers may not be in possesion of a brand 
new Quadcore Ultra-GPU High-End Desktop system. Read statistics for this.
Of course the situation in Germany and other western European countries 
differ from the situation in other parts of the world. Which some of you 
maybe don't take into account.

The Twitter bootstrap suite loads some MB of JS code at startup when 
being loaded. So there is also a tradeoff between how much computation 
power you want to take off the customers system. I guess if this 
direction is kept on TYPO3 mostly developed by Germans will be a system 
only suitable mostly for Germany (and other western European countries).
Which surely isn't the goal!


I have some idea about this task. I would like to discuss it in a thread 
on its own.


greetings,
Bernhard


More information about the TYPO3-team-core mailing list