Skip to content

Blocking characteristics #240

Answered by vincent-herlemont
agersant asked this question in Q&A
Discussion options

You must be logged in to vote

Native DB entirely delegates the management of storage to the redb backend (database) and it's necessary to refer to this documentation for details redb/design. Native DB can be seen as an overlay to redb. However, here are some brief responses:

In what circumstances do transaction operations (get, insert, remove, commit, etc.) end up performing disk I/O on the thread they were called?

Transaction operations perform disk I/O when accessing data not in cache or when writing changes to disk during a commit.

Is the above answer any different if the amount of managed data is below the cache_size?

Yes, if all data fits within the cache, read operations may avoid disk I/O, but writes still …

Replies: 1 comment 1 reply

Comment options

You must be logged in to vote
1 reply
@agersant
Comment options

Answer selected by agersant
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
2 participants