Aye :) But I think properly managing memory rather than aborting would be wise. If you need to take data in chunks then do so, and the tools support it, so manageability of this problem seems well within reach. Also, if you do know the max you need there is a php max memory setting in the ini file that is tweakable.
//Andrew On 14/03/07, Michel D'HOOGE <[EMAIL PROTECTED]> wrote: > > On Wednesday 14 March 2007 09:02, ved wrote: > > After > > processing 1500 records it fails with this error message > I already experienced that. My workaround is to check the amount of > available > memory at the end of the main loop and quit (cleanly) when there is only a > couple of MBs left. Since the batch is called every 5 minutes, it manages > to > cope with such not so frequent peakload... > -- > Michel > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "symfony developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/symfony-devs?hl=en -~----------~----~----~----~------~----~------~--~---
