etl: memoryDataProvider.Next to return zero-copy #19778
Description
Metadata
Metadata
Assignees
Type
Fields
Give feedbackNo fields configured for issues without a type.
{{ message }}
memoryDataProvider.Next to return zero-copy #19778
I see that bottleneck of
domains.Flush()ismemoryDataProvider.Next:I guess it's because - it copy data into in-buffers instead of return zero-copy
need investigate - and if not easy to fix: then combine with #19512 and make all providers zero-copy in same time.
(i think it's very visible on commitment history, but anyway seems tons of useless copies here)