For some workloads that read a lot of data once, it would be helpful if the reads could avoid trashing the cache. That is, an application could specify read_once=true or similar to WT_SESSION::open_cursor, and the reads via that cursor would set the WT_READ_DONT_NEED flag internally.
- is depended on by
-
SERVER-36631 Have the storage engine interface expose a reduced cache footprint read API
-
- Closed
-
-
SERVER-36068 Expose a user-accessible cursor option to avoid caching data from reads
-
- Closed
-
- is duplicated by
-
-
- Closed
-
- related to
-
-
- Closed
-