Router: Buckets, Sinks and Orders #516
No reviewers
parabit
Labels
No labels
bug
documentation
duplicate
enhancement
good first issue
help wanted
invalid
question
wontfix
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
parasitepool/para!516
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "route-buckets"
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?
Closes #509 and #511
Introduce Scheduler for routingto Add scheduler for routingAdd scheduler for routingto Router: Buckets and SinksRouter: Buckets and Sinksto Router: Buckets, Sinks and OrdersLGTM
@ -22,2 +22,4 @@TotalWork::from_raw(self.0 * 86_400.0 / HASHES_PER_DIFF_1 as f64)}pub fn target_hashrate(self) -> HashRate {Good target to always be at least on par to finish an order in a days time, not 100% sure if that logic holds when dealing with fractional PHd or orders that exceed supply, but this is an excellent improvement for now. 👍
yeah it scales up and down. I've standardized delivery time to 24h and I make a soft promise to target that hashrate for that amount until target_work reached
@ -267,38 +280,34 @@ impl Router {fn rebalance(&self) {Am I reading this right that it is going to spaz out a bit if an order is starving and we lack the hashrate to fully feed all open orders?
What do you mean by spaz? It should wont be able to point hashrate to that order, nothing else really happens