Using a large number of workers can result in many tiny bloblogs being created for small operations #46
Labels
No Label
No Milestone
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: reivilibre/yama#46
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
e.g. using
yama push
.Because we want a high level of concurrency here to hide latency from the network, this can result in e.g. 12 bloblogs less than a few kilobytes being created for a small push operation.
This could be cleaned up in a vacuum pass but it'd be nice to avoid that happening for small operations in the first place.
It's not sure how we could do that since a perfect solution involves predicting the future. But it might be possible to apply a heuristic or two.
Using a large number of workerscan result in many tiny bloblogs being created for small operationsto Using a large number of workers can result in many tiny bloblogs being created for small operations