[TYPO3-core] RFC #8649: Bug: No check on memory_limit in class.tx_impexp.php

Dmitry Dulepov [typo3] dmitry at typo3.org
Sat Jul 12 13:46:20 CEST 2008


Hi!

Dmitry Dulepov [typo3] wrote:
> Martin Kutschker wrote:
>> I can imagine that we add a memory limit field to be set in the EM to
>> impexp. Generally I think that such a special tool like impexp should
>> use all the memory it can et (via php.ini), so an extra config is ok (I
>> don't like hardcoded limnits).
>>
>> Mysql has also different (memory) setting for different parts of the
>> system (server, CLI, CLI-dumper, etc). So why can't we?
> 
> We can. But so far we had only one, system wide. If we change this, we 
> declare anyone can set this setting for whatever value and ignore 
> system-wide setting. So system-wide setting cannot be trusted anymore.
> 
> Most likely it will cause admins to disable changing this value at all...

I fight it in this thread actually because my memory values for each subsystem is very carefully chosen to divide memory optimally on the server between applications. So if application starts changing this memory as it wants and I cannot prevent it, my memory optimization goes to hell...

If it were only my problem, I can make a workaround. But I think there are others admins, who trust the system not to exceed defined quotas. Trusted system is a big thing. System that cannot be trusted is a bad thing.

-- 
Dmitry Dulepov
TYPO3 Core team
More about TYPO3: http://typo3bloke.net/
Subscribe: http://typo3bloke.net/rss.xml


More information about the TYPO3-team-core mailing list