Skip to content

R/W ops can get out of sync #140

@szarnyasg

Description

@szarnyasg

Moving a discussion on Slack here:

  • read ops & write ops are sent to different threads, read threads are a pool, write threads are long lived threads that are pinned to op streams
  • so reads and/or writes can outpace one another if the compression ratio is set too ambitiously…
  • passing all ops via a pool is a no-go, because it’s too slow
  • but what might make sense is to use those long lived threads for all ops
  • and assign reads to those long lived threads before even starting, so there is no need to feed ops to threads via a queue. rather, each thread would get an iterator that it simply exhausts

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions