GWA abstract.

.okwords

@@ -0,0 +1,66 @@
+01Hz
+0xc4
+10ms
+1ms
+al
+AndroBench
+AOSP
+App
+app
+Apps
+apps
+Barcode
+bursty
+CDF
+CONCAT
+Const
+DS
+equi
+ETL
+Eventbrite
+Facebook
+filesystem
+FTL
+Gmail
+interarrival
+JDBC
+Jeong
+JuiceSSH
+KakaoStory
+Kang
+KBS
+KitKat
+kong
+LINQ
+MobiGen
+MX
+offline
+OLAP
+OLTP
+ORMs
+OTA
+PhoneLab
+PlayerPro
+Pre
+pre
+Quickoffice
+runtimes
+smartphone
+smartphones
+Speedtest
+SQL
+SQLite
+sqlite
+StatusQuo
+subqueries
+SUBSTR
+TinyDB
+TPC
+TuneIn
+UB
+UPSERT
+UPSERTS
+VLC
+Wifi
+YCSB
+YouTube

sections/0-abstract.tex

@@ -1 +1,23 @@
-Embedded database engines such as SQLite are now found in most major operating systems, where they serve as a persistence layer for  user-facing applications.  This is especially true for modern mobile operating systems like Android. The performance of these engines directly impacts the power-consumption and response time of user-facing applications and the devices on which they are deployed. It is now more important than ever that we understand how such applications interact with their embedded databases, the environment in which these applications are run, and other factors such as power consumption, which impact and are impacted by database performance.  In this paper, we present the results of a long-running case study, tracing SQLite access patterns and run-time characteristics for applications on Android smart phones.  We outline our findings, present key features that distinguish user-facing smart phone database workloads from canonical server workloads, and propose the foundational characteristics of a benchmarking suite for mobile device databases based on our findings.
+Because embedded database engines such as SQLite provide a convenient data
+persistence layer, they 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 private structured data as well.
+%
+As a result, embedded database performance affects the response times and
+resource consumption of both the platforms that operation billions of
+smartphones and the millions of applications 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 produce queries and access
+patterns quite different from canonical server workloads.
+%
+We argue that evaluating smartphone embedded database will require a new
+benchmarking suite, and we use our results to begin to outline some of its
+characteristics.