Make the batch size configurable
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 598
- Forks
- 168
- Avg merge
- 1d 4h
- Merged PRs (30d)
- 86
Description
One conclusion from the memory analysis PoC is that the batch size can be used to reduce memory overall, but at the expense of much longer runtimes. This is a subjective trade-off so we should let users decide.
One option is we can add it to BaseRemote, and have the default plugin machinery use this as the batch size. Right now it defaults to 1000, so we would keep that default.
Another option is to have it be a setting so that all tasks will run with that option. That makes it an admin-only setting, and not one users can control.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading BaseRemote and the default plugin machinery that currently uses a batch size of 1000. Determine whether configuration belongs on BaseRemote or in an administrator setting, then verify that users can choose the memory/runtime trade-off while the default remains 1000.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100