Composer update "process killed"


i tryed to execute:

$ composer.phar update

and recieve:

Fatal error: Allowed memory size of 94371840 bytes exhausted (tried to allocate 71 bytes) in phar:///home/xxxxxxx/bin/composer.phar/src/Composer/DependencyResolver/RuleSetGenerator.php on line 123

the xxxxxxx is the user

and tryed to execute:

$ php -d memory_limit=256M ~/bin/composer.phar update


$ php -d memory_limit=512M ~/bin/composer.phar update

i receive this:

Yikes! One of your processes (php, pid 14331) was just killed for excessive resource usage.
Please contact DreamHost Support for details.

how can i execute composer update on dreamhost shared host?

the context: Framework Laravel 4


Hi! I see you already submitted a support ticket about this - Thanks so much! If you can reply to the email directly with the username you’re using, our team can proceed to investigate this with you. Thanks!


new clients, beware, dreamhost shared host alow to install composer, but the host is too slow to run “composer update”. No make sense it, you can install but impossible to use.


the response from Dreamhost: “I’m afraid that it may be best to look into using our VPS service. The processes coming from your account are too high to stay on our shared plan. Here’s a link with information on our VPS service if needed.”

the end of story: the command “composer update” its impossible to use in dreamhost shared host because the server is too slow and limited, bad host.


How many modules are you updating? My needs are modest, just two libraries, so I have no problem using composer. Shared does mean limited memory, so you have to work within those constraints no matter what process you are trying to run. Perhaps update a subset first, then the rest after?


Why do you need to use update? Run the update command on your development machine, which generates the .lock file for you. Then on the shared host just run composer install. This will use a let less memory! I have had the same thing happen to me, until I realized I did not need to run the update command on the shared host.