[8.x] Optional param for chunk size on scout:import #407
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Allow setting an optional chunk size when running a batch import.
This is particularly helpful if you'd like to index a model using a different batch size than the default set for the app. Ideally it may be nice to customize batch sizes per model, instead of a single shared config value to be used across the entire app.
This is a functional workaround as it exposes in the CLI an already available chunk size parameter in the
Collection::serializable
extension method.This is very useful for reducing the overhead of queries/update index calls for simpler indexable models. (For example, being able to batch 10k at a time instead of the default 500). Same applies for potentially complex indexable items where you'd want to reduce memory overhead by indexing less than the default at a time.