Jul 2026· International Conference on Information and Communicatiaon Technology· pp. 1-6· 0 citations· 15 references
Abstract
AWS Graviton processors present cloud architects with a critical cost-performance decision for relational databases, yet independent validation for real-world Online Transaction Processing (OLTP) workloads on managed services like Amazon Aurora PostgreSQL remains limited. This study provides a tier-aware evaluation comparing Graviton and Intel architectures across Aurora’s general-purpose (M-series) and burstable (T-series) instance families. We conduct controlled benchmarks using pgbench on architecturally equivalent general-purpose instances (db.m7g.large vs. db.m7i.large) and relevant burstable instances (db.t4g vs. db.t3). Results, validated with high statistical consistency (Coefficient of Variation ¡ 3%), reveal a decisive tier-dependent outcome. For general-purpose computing, Intel’s db.m7i.large delivers 29–68% higher throughput depending on workload and concurrency level and a 22.6% better cost-per-transaction ratio than the Graviton3-based db.m7g.large, despite a 6% higher hourly cost. Conversely, in the burstable tier, the newer Graviton2-based T4g instances provide 4–30% higher throughput, depending on instance size, and 18–29% better cost-performance compared to the older Intel T3 instances they commonly replace. This burstable advantage reflects both architectural improvements and a generational leap. Our findings demonstrate that optimal architectural selection depends on both instance family and generation, providing cloud architects a data-driven framework: choose Intel for performance-critical general-purpose workloads, and migrate to Graviton for cost-optimized burstable deployments replacing previous-generation Intel instances.
Framework and runtime selection for containerized microservices are usually guided by request-level benchmarks, yet deployment-facing costs often dominate operational expenditure in Kubernetes environments. This study empirically evaluates four such infrastructure characteristics: container image size, startup time, id...
Matej Šarić, Aleksander Radovan, D. Kučak· Applied Sciences· 0 citations
AddressSanitizer (ASan) is widely deployed in industrial C/C++ development, but its runtime and memory costs can limit routine use in continuous integration and production-like testing. Although many optimized ASan-like sanitizers have been proposed, heterogeneous workloads, configurations, and baselines make their pra...
Jia-Xin Xi, Cheng Wen, Zhi-Wei Lin et al.· Proceedings of the 41st IEEE...· 0 citations
Modern web applications are increasingly reliant on Object-Relational Mapper (ORM) frameworks to bridge the gap between high-level application logic and relational databases. However, in standard Create, Read, Update, and Delete (CRUD) architectures, the use of a unified data model often leads to significant performanc...
Justin Evan Surya, Kenny Jingga· International Conferences on...· 0 citations
Optimization of queries in RDBMSs have been one of the most important roadblocks as the rule-based optimizer s fail to scale to the non-linear nature of the new analytical workloads. Although Machine Learning (ML) models have demonstrated good latency predictability, their poor interpret-ability creates a Trust Ga...
Hanan Abed Alwally Abed Allah, عبدالله بن محمد بن عيد الساعدي, Saif Saad Khudhair· Journal of the College of B...· 0 citations
Modern OLTP applications, such as financial fraud detection and stock risk management, rely on analytical queries for real-time decision-making. In these scenarios, queries must access the freshest data without disrupting the performance of mission-critical transactions. We characterize them as
transaction-centric...
Ze-Shun Peng, Qin-Cheng Cai, Si-Yuan Wei et al.· Proceedings of the ACM on Ma...· 0 citations
We use cookies to run the site and, with your consent, for analytics and to show ads.
See our Cookie Policy.