Inserting large volumes of data into SQLite - speed issues

by Marco Nelissen » Thu, 03 Sep 2009 01:02:38 GMT


Sponsored Links
 Are you using bulkInsert?





--~--~---------~--~----~------------~-------~--~----~



Inserting large volumes of data into SQLite - speed issues

by Gavin Aiken » Thu, 03 Sep 2009 01:10:08 GMT


 Does the data NEED to be on the device? Can it not reside on a server?
Certainly you are better to manage the synchonisation yourself rather than
bundle the 120MB lib for downloading through the marketplace. This sort of
download needs to be resumable and I would recommend users only download
with a Wifi connection.

What sort of data is this?! It would have to be incredible to justify that
size to most users, I think with a 3 hour install you have lost 99% of the
user base without even knowing if the app is any good.

Gav





--~--~---------~--~----~------------~-------~--~----~


Sponsored Links


Other Threads

1. DialogTest#testOnWindowFocusChanged failure

I am occasionally getting an assert failure on line 699 of
DialogTest.java.  It is testing that it received an onFocusChanged()
callback after displaying a new window.

Seems to me there is a problem with this test:

mActivity.showDialog(DialogStubActivity.TEST_DIALOG_WITHOUT_THEME);

...starts displaying a new dialog box.  A little further down in the
test, it calls:

mInstrumentation.waitForIdleSync();

...apparently to wait for all messages to drain from the message
queue.  Then it checks a boolean flag to make sure the expected
callback happened:

assertTrue(d.isOnWindowFocusChangedCalled);

...and that is where I sometimes get a failure.



After putting in some debug prints, here is what I have discovered:

mActivity.showDialog() eventually calls
WindowManagerService.updateFocusedWindowLocked() which sends a
REPORT_FOCUS_CHANGE message.  Unfortunately the message is not
inserted in the same queue that mInstrumentation.waitForIdleSync() is
waiting for, afaict.  It's not even in the same process.  So sometimes
mInstrumentation.waitForIdleSync() returns before the
REPORT_FOCUS_CHANGE message has been processed which causes the assert
to fail.


Does this sound correct?  What is a good way to fix this?

Thanks

-- 
unsubscribe: android-porting+unsubscr...@googlegroups.com
website: 

2. Android on NO-MMU architecture

Hello all,
I have searched on this list and I have found this post *[android-porting]
Lego robotics controller (ARM7)  *which says that
android is not suitable for MMU-less architecture.

I am asking confirmation for this information.
This post is one year old, so maybe things are different now..

Thanks very much in advance for your help.

-- 
unsubscribe: android-porting+unsubscr...@googlegroups.com
website: 

3. Hide Phone Number in Dialer

4. Loading an image from a network stream

5. Android not taking up full screen size

6. Touch not working for listitem??

7. How to pass on extras to a custom intent?