I'm currently running the backend REST API for my game using Aurora MySQL, and I'm also considering switching to Aurora PostgreSQL. I'm curious about how these two engines compare when it comes to resource consumption and performance. Specifically, I'm wondering which engine tends to use more RAM or CPU under similar workloads. Additionally, I'm interested in their read/write throughput and latency: do they perform equally well, or is one better for high-concurrency transactional loads like those typical in game APIs that involve a lot of small queries? If you've had any experience with both, I'd love to know which one has cleaner resource usage. Have you noticed any significant performance differences for REST API workloads? Lastly, are there any unexpected issues with performance tuning or failover behavior between the two that I should be aware of? We're not heavily tied to MySQL features, so I'm open to switching if PostgreSQL proves to be more efficient or faster.
3 Answers
I've used both engines for quite some time, and generally, I haven't noticed a significant difference in resource usage. It really depends on your specific workload and the hardware you're using. I’d recommend running some tests yourself to see which one works best for your situation.
Certain types of loads might favor one database over the other. The main factors to consider are your management needs, resilience, and scaling options. Personally, I've found the serverless features a bit pricey, and performance can vary quite a bit. It's something to keep in mind.
Databases are complex, and finding benchmarks that fit your use case can be a challenge. My advice? Set up a small-scale test using PostgreSQL to see how it handles your workload and compare the performance directly. Also, dive into Aurora’s Postgres features to optimize your setup.
Thanks for the suggestion! I plan to test both engines soon, so that will definitely help.