Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Introduce a BulkIndexerPool abstraction #75

Open
marclop opened this issue Oct 13, 2023 · 0 comments
Open

Introduce a BulkIndexerPool abstraction #75

marclop opened this issue Oct 13, 2023 · 0 comments
Labels
enhancement New feature or request

Comments

@marclop
Copy link
Contributor

marclop commented Oct 13, 2023

Currently, the Appender creates bulkIndexers at runtime when the Appender is created. Instead of doing that, we could pass in a BulkIndexerPool, which contains a bounded pool of bulkIndexers and could be shared by multiple Appender instances to create a maximum memory boundary.

For fairness across different go-docappender instances, it would be good also to implement a per-go-docappender limit so one appended isn't potentially consuming all the bulk indexers.

@marclop marclop added the enhancement New feature or request label Oct 13, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant