Getting Priorities Straight: Improving Linux Support for Database I/O
Publikation: Bidrag til bog/antologi/rapport › Konferencebidrag i proceedings › Forskning › fagfællebedømt
Standard
Getting Priorities Straight: Improving Linux Support for Database I/O. / Hall, Christoffer; Bonnet, Philippe.
Proceedings of the 31st International Conference on Very Large Data Bases. 2005. s. 1116-1127.Publikation: Bidrag til bog/antologi/rapport › Konferencebidrag i proceedings › Forskning › fagfællebedømt
Harvard
APA
Vancouver
Author
Bibtex
}
RIS
TY - GEN
T1 - Getting Priorities Straight: Improving Linux Support for Database I/O
AU - Hall, Christoffer
AU - Bonnet, Philippe
N1 - Conference code: 31
PY - 2005
Y1 - 2005
N2 - The Linux 2.6 kernel supports asynchronous I/O as a result of propositions from the database industry. This is a positive evolution but is it a panacea? In the context of the Badger project, a collaboration between MySQL AB and University of Copenhagen, we evaluate how MySQL/InnoDB can best take advantage of Linux asynchronous I/O and how Linux can help MySQL/InnoDB best take advantage of the underlying I/O bandwidth. This is a crucial problem forthe increasing number of MySQL servers deployed for very large database applications. In this paper, we rst show that the conservative I/O submission policy used by InnoDB (as well as Oracle 9.2) leads to an under-utilization of the available I/O bandwidth. We then show that introducing prioritized asynchronous I/O in Linux will allow MySQL/InnoDB and the other Linux databases to fully utilize the available I/O bandwith using a more aggressive I/O submission policy.
AB - The Linux 2.6 kernel supports asynchronous I/O as a result of propositions from the database industry. This is a positive evolution but is it a panacea? In the context of the Badger project, a collaboration between MySQL AB and University of Copenhagen, we evaluate how MySQL/InnoDB can best take advantage of Linux asynchronous I/O and how Linux can help MySQL/InnoDB best take advantage of the underlying I/O bandwidth. This is a crucial problem forthe increasing number of MySQL servers deployed for very large database applications. In this paper, we rst show that the conservative I/O submission policy used by InnoDB (as well as Oracle 9.2) leads to an under-utilization of the available I/O bandwidth. We then show that introducing prioritized asynchronous I/O in Linux will allow MySQL/InnoDB and the other Linux databases to fully utilize the available I/O bandwith using a more aggressive I/O submission policy.
KW - Faculty of Science
KW - storage management
KW - IO
KW - Linux
KW - MySQL
KW - Oracle
M3 - Article in proceedings
SP - 1116
EP - 1127
BT - Proceedings of the 31st International Conference on Very Large Data Bases
Y2 - 29 November 2010
ER -
ID: 3184948