Closed nicolasca closed 10 years ago
There is an option called verifyIntegrity
that defaults to true
. With this option enabled, angular-cache attempts to verify that the contents of a given cache are correctly synchronized with what's in localStorage
on every operation. This incurs a performance a performance penalty for the benefit of data integrity. Try disabling this option for a performance improvement.
More reading:
http://jmdobry.github.io/angular-cache/configuration.html#verifyintegrity
@jmdobry ... fyi...
small update to docs ... they indicate verifyIntegrity defaults to false:
http://jmdobry.github.io/angular-cache/configuration.html#verifyintegrity
But in 2.3.0 verifyIntegrity defaults to true:
https://github.com/jmdobry/angular-cache/blob/2.3.0/src/angular-cache.js#L218
@findesk Good catch, the docs have been updated.
Performance will be improved in 3.0.0 #95
Thanks :)
I have a performance issue with angular-cache. I put around 50-60 in localstorage with a name like "blockReport_518_1_0". Then when my service is initialized, I found that it can take 1min. I made the following test:
It appears that it take 1 min between the two logs.
Am I missing some options, or is it an issue?