[TYPO3-mvc] findOneBy memory usage

Saverio Vigni s.vigni at hor-net.com
Wed Jul 18 17:41:20 CEST 2012


Ok using countByUrl the memory stays low, the problem i've found is that 
this method pass the count straight to the persistence backend not 
taking into account objects that has been added during the execution, 
instead of creating a temporary storage in my controller for those 
objects, i think i'll extend the persistence manager class replacing 
getObjectCountByQuery and scanning the result of 
$repository->getAddedObjects() summing then the 2 results.

Is it ok if after i've done i fill a bug on extbase forge and provide a 
patch?

Saverio

Il 18/07/12 15.20, Saverio Vigni ha scritto:
> Yes thank you :) actually i was aware of the issue and calling 
> persistAll everytime, this tool is not meant at the moment to be a 
> production ready, and almost an exercise for me to understand extbase 
> (well it's my first extbase little project :) ) but i really want to 
> understand how the memory management of extbase works and didn't 
> wanted do go straight to the database as i was playng with the idea of 
> writing a persistence class for redis (since i'm using it as cache 
> backend on many website and i'm very happy about it!) :)
>
> I'll digg deeper into extbase and try to figure out where the memory 
> consumption comes from...
>
> Saverio
>
> Il 18/07/12 14.09, Bastian Waidelich ha scritto:
>> Saverio Vigni wrote:
>>
>>> That's the route i was going to take as the last try because i would
>>> like to stay in the extabase "way of life" as much as possible...
>>
>> Did you read the rest of my post? ;)
>>
>> Best,
>>
>>
>
>
> _______________________________________________
> TYPO3-project-typo3v4mvc mailing list
> TYPO3-project-typo3v4mvc at lists.typo3.org
> http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-project-typo3v4mvc
>




More information about the TYPO3-project-typo3v4mvc mailing list