Go to file
Oliver Kennedy 90c658d8c1 adding project page 2015-10-12 19:00:46 -04:00
graphs minor formatting tweaks, some flow tweaks, and adding a conclusions section. 2015-06-21 13:29:25 -04:00
pytex Working. 2015-06-18 19:22:04 -04:00
sections Readthrough with some grammar and flow tweaks. Also fixing a few typos in the abstract. Nothing serious. 2015-07-21 19:35:01 -04:00
submitted Final tweaks 2015-08-30 22:53:37 -10:00
tables Adding text for fig 13,14 2015-06-20 18:09:27 -04:00
.gitignore Repo. 2015-06-18 17:54:45 -04:00
.okwords New. 2015-06-22 11:27:37 -04:00
Makefile Working. 2015-06-18 18:42:43 -04:00
README.md adding project page 2015-10-12 19:00:46 -04:00
aliascnt.sty Repo. 2015-06-18 17:54:45 -04:00
feedback.txt Feedback 2015-07-09 11:25:13 -04:00
llncs.cls Repo. 2015-06-18 17:54:45 -04:00
main.bib Statusquo bib entry 2015-06-20 18:39:13 -04:00
paper.tex Submitted files. 2015-06-23 14:21:51 -04:00
remreset.sty Repo. 2015-06-18 17:54:45 -04:00
splncs03.bst Repo. 2015-06-18 17:54:45 -04:00
sprmindx.sty Repo. 2015-06-18 17:54:45 -04:00

README.md

Pocket Data: The Need for TPC-MOBILE

Abstract

Embedded database engines such as SQLite provide a convenient data persistence layer and have spread along with the applications using them to many types of systems, including interactive devices such as smartphones. Android, the most widely-distributed smartphone platform, both uses SQLite internally and provides interfaces encouraging apps to use SQLite to store their own private structured data. As similar functionality appears in all major mobile operating systems, embedded database performance affects the response times and resource consumption of billions of smartphones and the millions of apps that run on them---making it more important than ever to characterize smartphone embedded database workloads. To do so, we present results from an experiment which recorded SQLite activity on 11~Android smartphones during one month of typical usage. Our analysis shows that Android SQLite usage produces queries and access patterns quite different from canonical server workloads. We argue that evaluating smartphone embedded databases will require a new benchmarking suite and we use our results to outline some of its characteristics.