Try to divide your fixtures in several files. Maybe propel will flush some memory by passing from one file to another.
(Never tried) On Jun 10, 5:47 pm, Steve Sanyal <[email protected]> wrote: > Thanks. I am on a shared server, so I don't know if that's possible? > The current memory limit is set to 128M as per phpinfo(). > > What's weird is the error is not always occurring, it's intermittent, > and the dataset has always been the same size, about 10K records. > > If I try the task 3 or 4 times, it will usually complete eventually. > I am not sure how that makes sense. > > On Jun 10, 11:22 am, Pierre Lecocq <[email protected]> wrote: > > > Try to increase the memory allocated to php. > > > /etc/php5/cli/php.ini > > /etc/php5/apache2/php.ini > > > The most important is the CLI one. > > > On Jun 10, 4:22 pm, Steve the Canuck <[email protected]> wrote: > > > > The propel:data-load task is running out of memory on my staging > > > environment. I have about 10K records to include in my initial load. > > > I don't have an issue on my laptop which I use for development, but I > > > run into problems in a shared hosting environment. > > > > Does anyone know of any workarounds to this or solutions? I read one > > > suggestion to write my own task - ideally if someone has already > > > created a generic alternative I might be able to use that. > > > > Thanks, > > > Steve --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "symfony users" 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-users?hl=en -~----------~----~----~----~------~----~------~--~---
