29cfa04c05
Data shreds are batched into MAX_DATA_SHREDS_PER_FEC_BLOCK shreds for each erasure batch. If there are residual shreds not making a full batch, then we cannot generate coding shreds and need to buffer shreds until there is a full batch; This may add latency to coding shreds generation and broadcast. In order to evaluate upcoming changes removing this buffering logic, this commit adds metrics tracking residual number of data shreds which don't make a full batch. |
||
|---|---|---|
| .. | ||
| benches | ||
| src | ||
| tests | ||
| .gitignore | ||
| Cargo.toml | ||
| build.rs | ||