Identifying performance issues has always been the holy grail of engineering. You want to be known as the software engineer who's able to diagnose and rectify the performance issue that came up in production. It really adds credibility to your engineering chops. We had an issue at work recently that

freeCodeCamp is a nonprofit organization offering free online coding courses and programming tutorials, covering topics such as web development, data science, and machine learning. Learners can gain practical coding skills, build real-world projects, and earn certifications to advance their careers in tech.

freeCodeCamp

AWS has a concept of an EC2 Compute Unit (ECU) which is their way of abstracting away having to think about the servers your application is running on. The idea is that AWS provides you with a baseline CPU utilisation beyond which you pay for the CPU time you consume.

How to Improve AWS Performance Without Spending More Money

So, How Am I Losing Money On Burst Credits?

<p>I’ve seen so many bloated systems running with huge infrastructure bills because of poorly written code and bloated architectures (usually the work of ‘non-coding’ architects). If you design systems for speed from the ground level it’s amazing how much performance you can squeeze out of modest hardware. Then, if your demand grows, drag the slider and go to the next level up.</p>


<p>Who runs their production on t*.micro instances?? Really? All well and good but this article is for bottom of the barrel kind of performance that wouldn’t be there if they took sizing even remotely seriously and used any of the appropriate type of instances.</p>
