[TYPO3-core] RFC #8649: Bug: No check on memory_limit in class.tx_impexp.php
Ingo Renner
ingo at typo3.org
Mon Jul 14 10:08:37 CEST 2008
Steffen Kamper wrote:
> Dmitry Dulepov [typo3] schrieb:
>> Hi!
>>
>> Martin Kutschker wrote:
>>> How often do you expect your users to use impexp?
>>
>> Not really often. Truly speaking never used myself for import, only
>> did export two or three times :)
>>
>>> Would you feel better if the memory limit setting for impexp would have
>>> to changed from the installer? Of course it would have to be more a
>>> general value for all importing/exporting features, eg also for fetching
>>> translations or an update of the extension list.
>>
>> Yes, this would be great. Something like "Larger memory limit for
>> memory-hungry modules". In fact, it is ideal solution because I would
>> prefer to have one memory limit for EM-like modules and another for
>> the rest of the system. Your idea is the best.
>>
>
> Hi,
>
> i don't think that it's the right way to increase memory for such
> memory-expensive script.
> In fact the script should be optimized not to use so much memory.
> With mysqldumper, a former project of mine, we had the same problems -
> saving GB-databases with memory- and timeout-limits of a normal
> webspace, and we solved it by partly doing this and calling the script
> again to continue at last position.
> Some kind of this technique could solve such problems impexp has, same
> in EM.
I'm afraid this is not the solution for the EM, too. The better solution
for the EM is to use newer techniques to parse the XML that are less
memory expensive instead.
See this presentation f.e.:
http://www.scribd.com/doc/3288339/rob-richardsstreaming-xml
I also have it as a pdf if you want it.
Ingo
--
Ingo Renner
TYPO3 Core Developer, Release Manager TYPO3 4.2
More information about the TYPO3-team-core
mailing list