> You go home. So you shut things down. Sorry for the rant, but this is usually wrong. The amount of people that just keeps their computer on is noticeable. And when I ask it's usually "just to avoid having to wait" or "I've always done that". I personally always hibernate my computer. When I turn it off it takes more time, but I'm already on the other side of the building so I don't care. When I turn it on it takes…
I always shutdown my machine at night and sometimes restart when I leave for lunch. I've noticed running Docker and other apps for a while makes my machine slower. I'm convinced there's a memory leak somewhere and restarting away fixes those issues.
Cutting down AWS cost by $150k per year simply by shutting things off
191–194 of 194 posts
Re: Cutting down AWS cost by $150k per year simply by shutting things off
#192Earlier quoted context omitted.
You being at peace with "non-monetary benefits" is what depresses wages and real rewards for you, but more importantly all your colleagues.
Just curious, do you feel the same way when someone chooses a job that pays less but has a better work life balance, or a shorter commute, or more opportunities for growth, or similar?
Re: Cutting down AWS cost by $150k per year simply by shutting things off
#193I've mentioned this before, in my company (big media company) I saw some S3 costs creeping up each month. I looked into it and it was a system we abandoned that was still copying files to this bucket. I reached out to the team and they turned it off, it saved us $1m a year. The higher-ups rewarded me by telling me that a team should have caught this so I should meet with them now.
You got rewarded with more meetings? Not a bonus?
Re: Cutting down AWS cost by $150k per year simply by shutting things off
#194I've mentioned this before, in my company (big media company) I saw some S3 costs creeping up each month. I looked into it and it was a system we abandoned that was still copying files to this bucket. I reached out to the team and they turned it off, it saved us $1m a year. The higher-ups rewarded me by telling me that a team should have caught this so I should meet with them now.
I work for a company called CloudFix, and we are solely focused on AWS costs. We do automated AWS cost optimization. We find one of two reactions when we deliver savings to customers: (A) "Hey wow, this is great! We are so excited to be saving from here on out." OR, (B) "This should have been caught earlier. $TEAM was supposed to be experts..." and then blame game starts. It is really unfortunate when institutions re…
The biggest problem they have is they have no business insight into what these costs are, and if we can reduce the cost without any kind of engineering, effort, or loss of performance.