You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@dacook has recently discovered that old and unused gems on servers just hang there, stagnant, waiting to crash the entire server as memory fills. They are a potential silent killer and you know how we feel about silent killers?
We get to them when they actually break everything, just like everything else we do.
For example, on DE there was about 9gb of unused old gems (over 20% of the disk!).
Acceptance Criteria & Tests
Add to the deployment/provision scripts an automated task to remove all old and unused gems. I'm not actually clear about how we'll do this so perhaps @dacook can add some more details.
The text was updated successfully, but these errors were encountered:
Thanks Lynne, I propose we remove all unused gems (including older versions) as part of each deploy. It turns out there's already a simple command for that (bundle clean).
If we do it before installing new gems, the previous version of any newly-upgraded gems will remain on the server until the next deploy, which will be helpful in the event of a rollback (although I'm not sure we've ever done that).
If any gem is removed that is later needed again, it can simply be re-downloaded.
I think it will be a very simple change, but will fight the temptation to do it right now..
Description
@dacook has recently discovered that old and unused gems on servers just hang there, stagnant, waiting to crash the entire server as memory fills. They are a potential silent killer and you know how we feel about silent killers?
We get to them when they actually break everything, just like everything else we do.
For example, on DE there was about 9gb of unused old gems (over 20% of the disk!).
Acceptance Criteria & Tests
The text was updated successfully, but these errors were encountered: