-
Notifications
You must be signed in to change notification settings - Fork 19
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
NoSQL #1411
base: develop
Are you sure you want to change the base?
NoSQL #1411
Conversation
As discussed in meeting:
|
e12de5d
to
93a6840
Compare
|
bc4173d
to
013f0c9
Compare
013f0c9
to
03ddb21
Compare
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## develop #1411 +/- ##
========================================
+ Coverage 12% 12% +1%
========================================
Files 265 258 -7
Lines 7382 7189 -193
========================================
Hits 819 819
+ Misses 6563 6370 -193 |
Closes #1391 closes #755
Used Object Box, which is not the ideal approach since it require new annotations on models and don't rely on the existing serialization.
Bus stops remain in
sqlite
since they are not working and fix code need to be written.Comparing SQlite and NoSQL
I run a simple experiment to compare the read and initialization times with my personal Exams data (around total 8 exams)
Conclusion
Since we had
9
databases and assuming they all boot up the same time as Exams, sequentially all of them would make171ms
to set up. Base on that, both of the technologies have similar db initialization times for a scenario using all the models (example: homepage with all of possible cards). However, read times were significantly decreased.