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
{{ message }}
This repository has been archived by the owner on Apr 18, 2023. It is now read-only.
Currently auction discovery and monitoring operates as a loop which kicks in on every new block and simply enumerates all auctions from 1 to kicks. This has several drawbacks:
Deleted auctions are being constantly queried over and over again, which will make the keeper work really slow as the number of historical auctions grows.
Output from bidding models doesn't get interpreted instantly, but only with each block. This can delay our bids by several seconds.
...
The plan is to replace it with a smarter mechanism, which should remember which auctions are already gone (and thus will not resurrect) and not query them constantly. At the same time any output from bidding models should get interpreted instantly.
The text was updated successfully, but these errors were encountered:
Currently auction discovery and monitoring operates as a loop which kicks in on every new block and simply enumerates all auctions from
1
tokicks
. This has several drawbacks:The plan is to replace it with a smarter mechanism, which should remember which auctions are already gone (and thus will not resurrect) and not query them constantly. At the same time any output from bidding models should get interpreted instantly.
The text was updated successfully, but these errors were encountered: