undefined | Better HN

0 pointsantirez11y ago0 comments

1324 -> 232. If you say 70% reduction VS 100% increment sounds like you are talking the same stuff and it is possible to compare 70 with 100.

The reality is even in the above edge case: 2x memory, 6x speed.

0 comments

Cthulhu_11y ago

This; interpreting performance numbers is hard. Also, memory nowadays is cheap, CPU power isn't.

porker11y ago

> Also, memory nowadays is cheap, CPU power isn't.

Unless you're running your deployment on a 512Mb or 1G VM. I've had composer max out swap on those too. Even with 2G RAM it's not been happy sometimes, so be interesting to see what difference this patch makes.

andrewryno11y ago

You shouldn't be running composer update on your deployment, just composer install which doesn't take as much memory since it doesn't have to resolve dependencies.

vertex-four11y ago

> Unless you're running your deployment on a 512Mb or 1G VM.

Question - why not run Composer locally, as part of deployment?

jayzalowitz11y ago

Yeah, i have had to move to more expensive ec2 instance on account of this very issue..

1 more reply

j / k navigate · click thread line to collapse