## Amazon’s Graviton CPUs: The Third Time’s the Charm?
### Initial Rejection: Graviton Overlooked
Atlassian initially cast aside Amazon’s Graviton CPUs, not just once but on two occasions. They were resolute in their decision not to implement them in production, sticking to the tried-and-true options. It was akin to walking into Greggs and consciously passing on a sausage roll—who would do such a thing?
### What Prompted Their Change of Heart?
After some deep contemplation, Atlassian ultimately recognized the potential. It emerged that Graviton had some features that made a difference. They discovered that with minor JVM adjustments and extensive testing, performance witnessed significant enhancements. Think of it as uncovering a hidden turbo mode in your outdated vacuum cleaner—yes, it was a revelation of that caliber.
### The Savings: More Cash in Their Hands
Following the adjustments, their expenses decreased by a respectable 10 percent. That’s sufficient to please even the most frugal Geordies. It’s like receiving a discount on your drinks at the pub: a genuine morale booster.
### Now Operating on Thousands of Instances
Atlassian is now utilizing thousands of server instances for their Jira and Confluence offerings on these Graviton CPUs. They transitioned from a position of disinterest to becoming enthusiastic advocates. It’s akin to someone finally giving CrossFit a shot and getting hooked.
## Summary
No More Resistance to Gravitons
Atlassian’s adoption of Amazon’s Graviton CPUs illustrates that even the most stubborn individuals can see reason when significant savings are presented. In technology, as in life, sometimes it’s beneficial to reconsider—perhaps two or three times. Or in this case, simply ensuring your vacuum cleaner is on turbo mode.
