-
Notifications
You must be signed in to change notification settings - Fork 37
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
Clustering #4
Comments
Every thread polls so they're on the same page as the other ones since that's one area Node.js falls short. I made the default config to be really aggressive at 100ms but I haven't noticed any high cpu usage from it though. |
Well, they could be kept on the same page by having a single thread deal exclusively with the daemon, sinking and sourcing everything to/from the stratum threads.
… On Mar 27, 2017, at 8:05 PM, Procrastinator ***@***.***> wrote:
Every thread polls so they're on the same page as the other ones since that's one area Node.js falls short. I made the default config to be really aggressive at 100ms but I haven't noticed any high cpu usage from it though.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub <#4 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AOexPasWFOkA-V4lJ3LZlWw5mkQ9UzC1ks5rqGrZgaJpZM4MniGV>.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I may be missing something, but it seems every thread is polling the daemon for work. Is that right? When I used z-nomp, I was also using "blocknotify", so I didn't notice the threads hammering the daemon the way they are now. I've turned "clustering" off, for the time being.
The text was updated successfully, but these errors were encountered: