-
Notifications
You must be signed in to change notification settings - Fork 2k
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
drop deprecated authentication_public_key
from pool config
#17959
Conversation
authentication_public_key
from pool config
|
Pull Request Test Coverage Report for Build 8935153853Details
💛 - Coveralls |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
sounds like this might fix the config load spam i've seen and reported a few times... but never made time to dig into. that'd be awesome. :]
thanks
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
"remove this a few versions after 1.3" - yea I guess we can do that :-)
Purpose:
As the TODO-comment explains:
I think it's safe to remove this. I discovered this as the current implementation of this backwards-compatibility also is not working right. It causes the
_periodically_update_pool_state_task
to run continuously. The reason is that callingadd_auth_key()
loads and re-saves the config file, thus bumping its "mtime". We use the mtime to determine whether ewe need to run this task early, rather than waiting the 60 secons we are supposed to.Running the task calls
add_auth_key()
resulting in continuously running the task, wasting CPU and disk I/O.This is especially apparent when you have multiple plotnfts.
Current Behavior:
When having many plotnfts, the farmer process pegs the CPU every 2 seconds. See the profile attached below.
New Behavior:
Having many plotnfts only causes the farmer process to perform the expensive work every 60 seconds. (There's still room for improvements in this regard, but this patch covers 95% of the problems).
Testing Notes:
I profiled the farmer process, depending on #17953
profile: