-
Notifications
You must be signed in to change notification settings - Fork 34
Open
Labels
Description
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
Reactions are currently unavailable