Same problem for me, with little less data I guess.

I solved it using array with doctrine ORM instead of heavy objects API, it was 
sufficient to what I needed. Using raw SQL will much likely use less memory.

As for php 5.2 I found using unset inside processing loops (even if the name is 
reused immediately after) seems to help GC on freeing memory sooner : on my 
import task, and my server, the growth of memory footprint was slowed down.

Regards,
Benoit



-----Original Message-----
From: pghoratiu <pghora...@gmail.com>
Sent: jeudi 3 juin 2010 00:33
To: symfony users <symfony-users@googlegroups.com>
Subject: [symfony-users] Re: batch import

I have done something similar and the memory leak problem was
difficult to solve. In my case
it was due to circular references between objects and I always had to
use unset() explicitely on
individual objects after saving them into the database.
Make sure the objects you are trying to save do not reference each
other because they can not
be free-d by the PHP garbage collector, also PHP 5.3 is somewhat
smarter about memory recycling (compared to PHP 5.2).

If you can not figure out where the problem is you should go with SQL
data inserts.

   gabriel


On Jun 2, 6:00 pm, f1gm3nt <f1gm...@gmail.com> wrote:
> I'm looking into doing batch imports with a symfony task. The issues
> I'm having are seg faults and running out of memory. Even after
> jacking the memory limit to 2gigs. Has anyone else ever done batch
> imports using a symfony task that can shed some light on how they did
> it?
>
> -f1g

-- 
If you want to report a vulnerability issue on symfony, please send it to 
security at symfony-project.com

You received this message because you are subscribed to the Google
Groups "symfony users" group.
To post to this group, send email to symfony-users@googlegroups.com
To unsubscribe from this group, send email to
symfony-users+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/symfony-users?hl=en

-- 
If you want to report a vulnerability issue on symfony, please send it to 
security at symfony-project.com

You received this message because you are subscribed to the Google
Groups "symfony users" group.
To post to this group, send email to symfony-users@googlegroups.com
To unsubscribe from this group, send email to
symfony-users+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/symfony-users?hl=en

Reply via email to