Empirical analysis of database server scalability using an N-tier benchmark with read-intensive workload

  • Authors:

  • Simon Malkowski;Deepal Jayasinghe;Markus Hedwig;Junhee Park;Yasuhiko Kanemasa;Calton Pu

  • Affiliations:

  • CERCS, Georgia Institute of Technology, Atlanta;CERCS, Georgia Institute of Technology, Atlanta;Albert-Ludwigs-University, Platz der Alten Synagoge, Freiburg, Germany;CERCS, Georgia Institute of Technology, Atlanta;Fujitsu Laboratories Ltd., Nakahara-ku, Kawasaki, Japan;CERCS, Georgia Institute of Technology, Atlanta

  • Venue:
  • Proceedings of the 2010 ACM Symposium on Applied Computing
  • Year:
  • 2010

Quantified Score

Hi-index 0.00

Visualization

Abstract

The performance evaluation of database servers in N-tier applications is a serious challenge due to requirements such as non-stationary complex workloads and global consistency management when replicating database servers. We conducted an experimental evaluation of database server scalability and bottleneck identification in N-tier applications using the RUBBoS benchmark. Our experiments are comprised of a full scale-out mesh with up to nine database servers and three application servers. Additionally, the fourtier system was run in a variety of configurations, including two database management systems (MySQL and PostgreSQL), two hardware node types (normal and low-cost), and two database replication techniques (C-JDBC and MySQL Cluster). In this paper we present the analysis of results generated with a read-intensive interaction pattern (browse-only workload) in the client emulator. These empirical data can be divided into two kinds. First, for a relatively small number of servers, we find simple hardware resource bottlenecks. Consequently, system throughput increases with an increasing number of database (and application) servers. Second, when sufficient hardware resources are available, non-obvious database related bottlenecks have been found that limit system throughput. While the first kind of bottlenecks shows that there are similarities between database and application/web server scalability, the second kind of bottlenecks shows that database servers have significantly higher sophistication and complexity that require in-depth evaluation and analysis.