-
Notifications
You must be signed in to change notification settings - Fork 168
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
Database file growth rate varies extremely #35
Comments
Please check your coverage here: https://ci.realm.io/job/realm/job/realm-core-private/job/PR-35/1/Diff_Coverage |
Please check your coverage here: https://ci.realm.io/job/realm/job/realm-core-private/job/PR-35/2/Diff_Coverage |
Check the performance result here: https://ci.realm.io/job/realm/job/realm-core-private/job/PR-35/1/Performance_Report |
Check the performance result here: https://ci.realm.io/job/realm/job/realm-core-private/job/PR-35/2/Performance_Report |
Check the performance result here: https://ci.realm.io/job/realm/job/realm-core-private/job/PR-35/3/Performance_Report |
Please check your coverage here: https://ci.realm.io/job/realm/job/realm-core-private/job/PR-35/4/Diff_Coverage |
Check the performance result here: https://ci.realm.io/job/realm/job/realm-core-private/job/PR-35/4/Performance_Report |
Please check your coverage here: https://ci.realm.io/job/realm/job/realm-core-private/job/PR-35/5/Diff_Coverage |
Check the performance result here: https://ci.realm.io/job/realm/job/realm-core-private/job/PR-35/5/Performance_Report |
Please check your coverage here: https://ci.realm.io/job/realm/job/realm-core-private/job/PR-35/6/Diff_Coverage |
Check the performance result here: https://ci.realm.io/job/realm/job/realm-core-private/job/PR-35/6/Performance_Report |
When adding small lumps of data through many individual write transactions, the rate of growth of the database file is sometimes extremely high, and sometimes it is not.
With about 4000 transactions each one adding a single row to a simple two-column table, the database file generally grows to about 2GiB, which seems pretty excessive.
In some cases though, this does not happen, and the database file size remains at a few hundred KiB, and that is for the exact same sequence of transactions.
To me, this looks like an indication of a bug.
The text was updated successfully, but these errors were encountered: