Skip to content
Hallway
0:00 / 0:00

#android#sqlite#jni

Google I/O 2012 - Doing More With Less: Being a Good Android Citizen

Google for Developers

2.6M subscribers • 20 videos on Hallway

YouTube
  • Recommended by 1 person: 1 on Stack Overflow and its sister sites.
  • Presented by Jeff Sharkey
  • Made by the vendor. The company whose product it covers made or sponsored it.
  • May be out of date. The tools, versions or practices it shows have likely moved on.

Intermediate. Assumes working knowledge.

28K views14 years ago1 recommendation

Mobile developmentSystems programmingAndroid and Jetpack ComposePerformance and optimizationSQLite

Jeff Sharkey shares advanced techniques to optimize Android apps for CPU, RAM, and I/O efficiency, including SQLite and JNI best practices.

Jeff Sharkey Faster and lighter is better, especially on mobile devices with limited resources. Learn advanced techniques to optimize for CPU, RAM, and I/O efficiency, and best practices for using JNI and SQLite. For all I/O 2012 sessions, go to developers.google.com/io/

Why it's here

1 person recommends this

What people say. Recommended for its insights on handling SQLite database operations and concurrency on Android.

Moments people linked to

esilveron Stack Overflow • Recommends

Folks, I'm looking for a design pattern that enables a UI thread to interact with a client-side SQLite database that may have bulk inserts (taking 10s of seconds), quick inserts, and reads, and doesn't block the UI thread. I would like advice on whether or not I am using the optimal design pattern for this, as I have been recently debugging deadlock and synchronization issues and I am not 100% confident in my final product. All DB access is now bottlenecked through a singleton class. Here is pseudocode showing how I am approaching writes in my singleton, DataManager: public class DataManager { private SQLiteDatabase mDb; private ArrayList<Message> mCachedMessages; public ArrayL…
7View the answer