TY - GEN
T1 - A method for analysis and solution of scalability bottleneck in DBMS
AU - Horikawa, Takashi
AU - Fukuda, Akira
PY - 2010/11/22
Y1 - 2010/11/22
N2 - Many-core systems differ from traditional multi-processor systems in performance characteristics and sometimes behave in unfamiliar ways for us. This can lead us facing performance troubles from unknown causes, requiring long time to fix them. To address those situations it is important for us to accumulate technology and know-how on performance of multi-core systems through a plenty of case studies. This paper describes a case study on unusual phenomena of a many-core based system in executing DBT-1 transactions with MySQL; where system throughput was decreased with the increase of the number of cores, an appearance of a scalability bottleneck. The root-cause analysis based on several measurements of the system has succeeded to reveal that the problem was caused from an interaction between two bottlenecks at the different layers, hardware and software, which is hardly found in traditional systems. The bottleneck at the hardware layer has been alleviated by introducing a newly developed lock mechanism that the analysis results suggested. Although the problem may be particular to the system, we, however, believe that the method and process to identify the root cause are of wide use for various scalability bottlenecks.
AB - Many-core systems differ from traditional multi-processor systems in performance characteristics and sometimes behave in unfamiliar ways for us. This can lead us facing performance troubles from unknown causes, requiring long time to fix them. To address those situations it is important for us to accumulate technology and know-how on performance of multi-core systems through a plenty of case studies. This paper describes a case study on unusual phenomena of a many-core based system in executing DBT-1 transactions with MySQL; where system throughput was decreased with the increase of the number of cores, an appearance of a scalability bottleneck. The root-cause analysis based on several measurements of the system has succeeded to reveal that the problem was caused from an interaction between two bottlenecks at the different layers, hardware and software, which is hardly found in traditional systems. The bottleneck at the hardware layer has been alleviated by introducing a newly developed lock mechanism that the analysis results suggested. Although the problem may be particular to the system, we, however, believe that the method and process to identify the root cause are of wide use for various scalability bottlenecks.
UR - http://www.scopus.com/inward/record.url?scp=78349249058&partnerID=8YFLogxK
UR - http://www.scopus.com/inward/citedby.url?scp=78349249058&partnerID=8YFLogxK
U2 - 10.1145/1852611.1852639
DO - 10.1145/1852611.1852639
M3 - Conference contribution
AN - SCOPUS:78349249058
SN - 9781450301053
T3 - ACM International Conference Proceeding Series
SP - 139
EP - 146
BT - Proceedings of Symposium on Information and Communication Technology, SoICT2010
T2 - Symposium on Information and Communication Technology, SoICT 2010
Y2 - 27 August 2010 through 28 August 2010
ER -