Excited to see this new release. Seems to me this would (slightly?) negatively impact query performance for recent data (when the query concerns data is both in O3 and persisted zones), is that the case?
Query performance would be affected in so far as ingest jobs share the same thread pool as query jobs. As I am writing this I am also realising that perhaps we should have an option to separate these jobs... If we ignore resource usage and commit() latency, query performance would remain unaffected. Reader remains lockless largely unchanged code-wise. This was one of our major objectives to maintain data model as seen by the readers. I hope I'm making sense here?
