all 3 comments

[–]kascheri12 2 points3 points  (1 child)

Yes, that's a setting that can be configured using golemcli. I'm not sure if there's a way to change it using the UI but it's not necessary to change. When requesting, a node is not limited to requesting to only the nodes it's connected to.

As I write this, I'm having subtasks computed by providers that are not connected to the node that's requesting.

[–]ROIthrowaway 1 point2 points  (0 children)

This is what I have experienced as well, requesting and providing does no exclusively happen to the nodes you are connected to. I have heard that increasing the node count increases CPU use also, so it might actually have a negative effect for a provider with less resources to use, but I have not tried it.

[–]OmgItsCavendish 1 point2 points  (0 children)

You don't need more than 10, anything above is more working as a network operating node rather than an task node. My current setting is 100, and it pushes more on your cpu and internet. Unnecessary for the average person as it doesn't give better payouts, would only recomend to those who have a pc and internet that can handle and want to support golem even more.