Performance question about dexie.js HOT 7 CLOSED

adding transaction around it for Dexie helps a bit:

https://gist.github.com/anonymous/f37c9e6a95ceda2a529d

down to 22sec on mobile

from dexie.js.

looking at the chrome tools lots of time is wasted by this:
function fakeAutoComplete(fn) {
var to = setTimeout(fn, 1000);
clearTimeout(to);
}

can this be changed/removed/improved?

from dexie.js.

When coding with visual studio, those lines are priceless but we should have a build script that removes them in the release / minified version. I did a simple profiling of that sequence last year but came to the conclusion that they really fast in the particular browser i tested it in (probably some version of chrome, opera or ie) but did not dig so deep into it.

There is a general problem that Dexie doesn't have a build script that I hope that someone could help or with.

from dexie.js.

That piece of code is not needed and does nothing. It's just a way to improve the IDE 's code completion. Once a build script is in place (grunt, gulp or so), i'll remove those calls from the minified version.

What you can do right now, is either to remove the code in fakeautocomplete(), or to remove all calls to it. Will not affect behavior at all. Sorry I wasn't more clear in my last answer about the actual code change you could do.

from dexie.js.

The calls to setTimeout()/clearTimeout() are now removed. However, when testing performance with chrome/opera/ie/firefox, this change is not noticable. Haven't tested on safari though.

from dexie.js.

David, the difference for me was noticeable on mobile devices.

from dexie.js.

Mobile devices is a common use case for the library so hopefully this fix might improve performance a little then.

Thanks!
David

from dexie.js.