You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, the frames_per_batch parameter is uniformly applied across all workers, which can lead to suboptimal utilisation of computational resources when dealing with heterogeneous environments per worker. One might want to build a batch with different fraction of the batch's frames per worker to account for specifics in the environments.
Solution
I propose that _MultiDataCollector exposes both frames_per_batch: int | None and frames_per_batch_worker: Sequence[int] | None. These should be mutually exclusive and in the case were frames_per_batch_worker is provided, frames_per_batchcan be computed as sum(frames_per_batch_worker).
I'll propose a PR in this direction.
Alternatives
An alternative would be to implement a new Collector handling this. This will lead to a load of code duplication for little to gain.
Additional context
Checklist
I have checked that there is no similar issue in the repo (required)