On Thursday 15 March 2007 22:24, Andrew Backer wrote: > create another instance of the batch after the first one completed (and > processed, say, 50 records). Well, this is more or less already what I do: quit the batch when the memory is nearly exhausted, and wait for the next call (which is scheduled every 5 minutes).
I didn't search already, but the correct way of optimizing the process is to use a profiler (never used one before with PHP) to find which class uses most of the memory and then try to correct it. A good candidate I identified is a fixed, small table with description of defects and that is highly referenced by another, big table containing the defects. I assume that by default, even with the Propel JoinTable method, new instances of the defect descriptions are created even if it was already used by another defect. So when I batch-handle my defects, a lot of memory is stupidly wasted. -- Michel
pgptbSK3AP6IV.pgp
Description: PGP signature
