android - Why apply() is no faster than commit() in SharedPreferences.Editor -


i learned difference between apply() , commit() of sharedpreferences.editor. apply() said asynchronous , safe run on ui thread; commit() said synchronous , not suitable run on ui thread. did simple test click listener in mainactivity:

sharedpreferences sharedpreferences = mainactivity.this.getsharedpreferences("synced", 0); sharedpreferences.editor editor = sharedpreferences.edit(); (int = 0; < 100000; ++i) {     editor.putstring("index" + i, "index" + i); } log.e("test", system.nanotime() + " sync "); editor.commit(); log.e("test", system.nanotime() + " sync " + sharedpreferences.getstring("index99999", "null"));  sharedpreferences sharedpreferences2 = mainactivity.this.getsharedpreferences("asynced", 0); sharedpreferences.editor editor2 = sharedpreferences2.edit(); (int = 0; < 100000; ++i) {     editor2.putstring("index2" + i, "index2" + i); } log.e("test", system.nanotime() + " async "); editor2.apply(); log.e("test", system.nanotime() + " async " + sharedpreferences2.getstring("index299999", "null"));

i run several time , received same result this:

05-25 01:11:44.608 16109-16109/darklord.preferencestest e/test: 1295614410392 sync  05-25 01:11:44.667 16109-16109/darklord.preferencestest e/test: 1295669350041 sync index99999 05-25 01:11:45.257 16109-16109/darklord.preferencestest e/test: 1296262306521 async  05-25 01:11:45.317 16109-16109/darklord.preferencestest e/test: 1296317374397 async null

i expecting apply() must faster commit(), result turned out same. both not suitable run on ui thread. why happens?

edit: log should be

05-25 01:11:44.608 16109-16109/darklord.preferencestest e/test: 1295614410392 sync  05-25 01:11:44.667 16109-16109/darklord.preferencestest e/test: 1295669350041 sync index99999 05-25 01:11:45.257 16109-16109/darklord.preferencestest e/test: 1296262306521 async  05-25 01:11:45.317 16109-16109/darklord.preferencestest e/test: 1296317374397 async index249999

i testing on emulator api 17.

the problem you're reading values in-memory

sharedpreference created before.

according documentation,

apply() commits changes in-memory sharedpreferences starts asynchronous commit disk

therefore, in-memory sharedpreference updated immediately.


-

Comments

Post a Comment

Popular posts from this blog

scala - 'wrong top statement declaration' when using slick in IntelliJ -

Image
i'm porting project scala 2.9 2.10, therefore have use slick instead of scalaquery. i'm using slick 2.1.0 since supports ms access. according this tutorial , upgrade guide changed robs object class , added val robs : why error message wrong top statement declaration , how rid of it? edit: i'm new scala... according this question seems can't put val outside of methods or classes, right? code above directly in packge. right approach slick then? should move code in class or trait? according this changed val robs = tablequery[robs] to object robs extends tablequery(new robs(_)) {} . no warnings or errors anymore. :)
Read more

c# - DevExpress.Wpf.Grid.InfiniteGridSizeException was unhandled -

Image
when using devexpress, see error: devexpress.wpf.grid.infinitegridsizeexception unhandled message="by default, infinite grid height not allowed since grid rows rendered , hence grid work slowly. fix issue, should place grid container give finite height grid, or should manually specify grid's height or maxheight. note can avoid exception setting gridcontrol.allowinfinitegridsize static property true, in case grid run slowly." the problem dxgrid has infinite height. to fix, set height non-infinite. snoop absolutely invaluable this: if "height" xaml element infinite (i.e. 0 or nan ), can set using one of following: option 1: height="{binding path=actualheight, relativesource={relativesource mode=findancestor, ancestortype=uielement}}" option 2: verticalalignment="stretch" option 3: height="auto" hint: use verticalalignment="stretch" if child of grid <rowdefinition height=
Read more

PySide and Qt Properties: Connecting signals from Python to QML -

i trying run simple pyside appliccation design made in qml. call function in qml python in separated thread. i have following qml view: import qt 4.7 rectangle { visible: true width: 100; height: 100 color: "lightgrey" text { id: datestr objectname: "datestr" x: 10 y: 10 text: "init text" font.pixelsize: 12 function updatedata(text) { datestr.text = qstr(text) console.log("you said: " + text) } } } here application: some imports.... #!/usr/bin/python import sys import time pyside import qtdeclarative, qtcore pyside.qtgui import qapplication pyside.qtdeclarative import qdeclarativeview the qthread worker.... #worker thread class worker(qtcore.qthread): updateprogress = qtcore.signal(int) def __init__(self, child): qtcore.qthread.__init__(self) self.child = child def run(self):
Read more