Android I/O Stack:
The Android I/O stack consists of elaborate and mature components (SQLite, the EXT4 file system, interrupt-driven I/O, and NAND-based storage) whose integrated behavior is not well-orchestrated, which leaves a sub-stantial room for an improvement. We overhauled the block I/O behavior of five file systems (EXT4, XFS, BTRFS, NILFS, and F2FS) under each of the five different modes of SQLite. We found that the most significant inefficiency originates from the fact that file system journals the database activity.Smartphones, tablets, and smart TVs,have become mainstream computing devices and are quickly replacing their predecessor, PCs. Smartphones and tablets have become the dominant source of DRAM consumption and account for 45% of Internet web browsing. They are becoming the personal computer. This work was done while the author was a graduate student renowned university devices for a variety of applications, including so-cial network services, games, cameras, camcorders, mp3 players, and web browsers. The application performance of a smartphone is not governed by the speed of its airlink, Wi-Fi, but rather by the storage performance, which is currently uti-lized in a quite inefficient manner . Furthermore, one of the main sources of this inefficiency is an excessive I/O activity caused by uncoordinated interactions between EXT4 and SQLite Despite its significant implications for the overall smartphone performance, the I/O subsystem behavior of smartphones has not been studied nearly as thoroughly as those in enterprise servers web servers OLTP servers and desktop PCs
No comments:
Post a Comment