# Performance of AWS Graviton instances for MongoDB

**URL:** <https://forums.percona.com/t/performance-of-aws-graviton-instances-for-mongodb/38066>\
**Category:** MongoDB\
**Created:** [May 22, 2025, 4:34pm UTC](https://forums.percona.com/t/performance-of-aws-graviton-instances-for-mongodb/38066 "2025-05-22T16:34:18Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Stateros](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/stateros/32/2490_2.png) [@Stateros](https://forums.percona.com/u/Stateros)\
**Post date:** [May 22, 2025, 4:34pm UTC](https://forums.percona.com/t/performance-of-aws-graviton-instances-for-mongodb/38066/1 "2025-05-22T16:34:18Z")

</div>

**Hi folks,**

If you’re using Percona Server for MongoDB—especially in Kubernetes—could you please share your thoughts on the performance of Graviton instances? If you can compare them with Intel/AMD architectures, that would be super helpful.

I’m asking because of an extremely negative experience we had when migrating a stable MySQL setup from Intel to Graviton in an effort to reduce costs this year.