Use non-blocking I/O for lsm_store #19

Closed
opened 2023-11-16 17:16:44 +00:00 by Jef Roosens · 1 comment

Both the db files & the entry data files currently use blocking I/O. Ideally the application solely uses non-blocking I/O, so these file accesses should also be non-blocking.

Both the db files & the entry data files currently use blocking I/O. Ideally the application solely uses non-blocking I/O, so these file accesses should also be non-blocking.
Jef Roosens added the
Kind/Enhancement
label 2023-11-16 17:16:44 +00:00

After some research, it seems that it isn't actually possible to set a regular file to non-blocking, as the kernel would stil need to block if data needs to be retrieved from the file system.

Perhaps we could add some manual caching to the LSM store that relegates this, but for the way this issue's currently phrased this isn't possible.

After some research, it seems that it isn't actually possible to set a regular file to non-blocking, as the kernel would stil need to block if data needs to be retrieved from the file system. Perhaps we could add some manual caching to the LSM store that relegates this, but for the way this issue's currently phrased this isn't possible.
Sign in to join this conversation.
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: Chewing_Bever/lander#19
There is no content yet.