Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature request: controlled sealing #1

Open
bobdubois opened this issue Oct 20, 2023 · 2 comments · May be fixed by #2
Open

Feature request: controlled sealing #1

bobdubois opened this issue Oct 20, 2023 · 2 comments · May be fixed by #2
Assignees

Comments

@bobdubois
Copy link
Contributor

Currently the only sensible way to control the amount of deals per hour or day that hits the sealing pipeline is:

  • import X amount of deals and kill spader OR
  • limit the dir_size variable to the size of the deals the sealing pipeline can handle

A more flexible way to control the amount of deals per hour or per day would be favorable. I know how many deals my pipeline can process per hour and it would be useful to feed it just enough so there is a continuous flow of deals at maximum throughput for the miner without choking it.

@LexLuthr LexLuthr self-assigned this Oct 20, 2023
@LexLuthr LexLuthr linked a pull request Oct 20, 2023 that will close this issue
@LexLuthr
Copy link
Owner

@bobdubois Can you please test the new branch in #2? Please make sure to let the current deals complete and then use a new directory to test.

@bobdubois
Copy link
Contributor Author

pulled the code and running spade.py with the new commit.
No deals incoming (yet) because of datacap issues on the tenant I see eligible deals for.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants