When I did my last benchmark on the Android I got a question if I had tried out DB4O on Android, something I had not. So I had to try it out, to see how it was to use on the Android platform and compare it to SQLite and Perst. Using object oriented databases makes it alot easyer to develop applications as you can think "objects" all though out the development process, where you don't have to think about converting the results back into obejcts again. Using DB4O on android worked completely painless, and after some searching I found a compatible version of the TestIndex application for DB4O that I could integrate in the android. Below are the results for the emulator, I hope that i can test it on the ADP1 later today. How did I test ? I ran the test index application several times until I got some stable / reliable results.
Here is a graph of the results on the emulator.
| Perst-Emulator
| SQLite-Emulator
| DB4O-Emulator
|
insert
| 11465
| 67420
| 36980
|
search
| 9601
| 90328
| 226624
|
iterate
| 6578
| 4504
| 39405
|
delete
| 18408
| 59998
| 71463
|
If we look at the results we see that the only thing that is really standing out is the search on the DB4O, I have no good explanation for this.
Posts
Hi! Thaks for sharing this.
ReplyDeleteCan you point me to where you found the db4o implementation of the test?
Is there a chance you can share the full source code for your implementation?
Best! (thx again)
Sure thing, here's the original DB4O TestIndex which I slightly modified/updated. I can try and upload the source for whole application in the weekend, just need to clean it abit up.
ReplyDelete