Skip to content

Сustom iterator over iters for View.Iterator() #482

@a1eks3y

Description

@a1eks3y

I ran into a use case where the current mergeIterator implementation introduces overhead due to its internal heap usage during iterator.Next(), while its ordering and preloading behavior is unnecessary for this access pattern.

In my case:

  • iterators are consumed only once
  • data comes from MemoryStorage
  • ordering and preloading are not needed

Because of that, heap-based merging, ordering, and preloading add cost without improving correctness for this scenario.

It would be useful if mergeIterator could be replaced, similar to how storage implementations are provided via a builder.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions