DBS-C01 · Question #122
A large retail company recently migrated its three-tier ecommerce applications to AWS. The company's backend database is hosted on Amazon Aurora PostgreSQL. During peak times, users complain about…
The correct answer is A. Modify the application to commit transactions in batches. https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraPostgreSQL.Referenc "This wait most often arises when there is a very high rate of commit activity on the system. You can sometimes alleviate this wait by modifying applications to commit transactions in…
Question
A large retail company recently migrated its three-tier ecommerce applications to AWS. The company's backend database is hosted on Amazon Aurora PostgreSQL. During peak times, users complain about longer page load times. A database specialist reviewed Amazon RDS Performance Insights and found a spike in IO:XactSync wait events. The SQL attached to the wait events are all single INSERT statements. How should this issue be resolved?
Options
- AModify the application to commit transactions in batches
- BAdd a new Aurora Replica to the Aurora DB cluster.
- CAdd an Amazon ElastiCache for Redis cluster and change the application to write through.
- DChange the Aurora DB cluster storage to Provisioned IOPS (PIOPS).
How the community answered
(36 responses)- A56% (20)
- B28% (10)
- C11% (4)
- D6% (2)
Explanation
https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraPostgreSQL.Referenc "This wait most often arises when there is a very high rate of commit activity on the system. You can sometimes alleviate this wait by modifying applications to commit transactions in batches. " https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/apg-waits.xactsync.html
Topics
Community Discussion
No community discussion yet for this question.