This app was mentioned in
with an average of
I'm not going to weigh in on any of the debates. I wouldn't say I'm "over it", but lets say energies are currently focused elsewhere. However, any more interesting tests on performance are fun to tinker with, and this discussion has been generating pull requests on my "benchmark", which is appreciated and I'll keep pushing updates to the store.
Realm isn't a relational db, but I put it in there because whatever. I put benchmark in quotes above because they're all highly skewed and don't much reflect reality, but you get a sense of which frameworks are clearly doing the wrong thing. If you can't do simple inserts and queries in less than 2x of the best time you're probably a hot mess under the hood. I think we should all agree on that.
I think Kevin Galligan made great job with his benchmark - a lot of different libraries, open source code base and it's quite up-to-date. If anybody is interested, here is a link to benchmark app available at Google Play store, which was updated the last time at 9th July - everybody can run it and decide ;)
/u/greenrobot_de when I have a moment I'll try to pull request with upgrade of DbFlow to latest version, but imho it's a little bit unfair to say that your orm would have been better if DbFlow had been upgraded. I don't know what's changed between DbFlow v2 and v3, but sometimes devs prefer to use older version of library - Dagger is a good example because of 'override' feature.
We had a side conversation on the site. For the record, I did try requery. Its very slow, at least in my tests. Reflection is not as bad as is believed, and certainly other parts of your code can slow things down. Not that performance is the only consideration, but its a big one. I allow that requery is new, so maybe performance will pick up, but its slow now. You can try on your device with the benchmark: [link] To see full discussion, look at blog post again, in comments.
Article Related Links
Better late than never!