ini_set('memory_limit', '128M');
BUT hang on. Do you really want to just throw more memory at the problem?
Why not look at better ways to optimise your code to use less memory? For
example, unset() variables and arrays as you finish using them. Use
resultset methods (such as doSelectRS or doSelect
You can also try setting the memory_limit using -d option:
php -d memory_limit=512 symfony
On Nov 30, 4:39 pm, Macvek wrote:
> Hi,
>
> I don't think so. It is global PHP property.
> You can try running this task locally, on your PC, and then upload the
> results to remote server.
>
> Building pr
You can also try setting the memory_limit using -d option:
php -d memory_limit=512 symfony
On Nov 30, 4:39 pm, Macvek wrote:
> Hi,
>
> I don't think so. It is global PHP property.
> You can try running this task locally, on your PC, and then upload the
> results to remote server.
>
> Building pr
Hi,
I don't think so. It is global PHP property.
You can try running this task locally, on your PC, and then upload the
results to remote server.
Building propel database can take some time, especially when there are
many relations.
Regards,
Maciej Aleksandrowicz
2010/11/30 HAUSa :
> Can I conf
Can I configure this in the .htaccess as well?
On 30 nov, 17:31, Macvek wrote:
> Hi,
>
> You should edit 'memory_limit' in your php.ini. I've set it to 128M
> and every task works well.
>
> Regards,
> Maciej Aleksandrowicz
>
> 2010/11/30 HAUSa :
>
> > If I run a task created in my lib/task folder
