Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.
Sign upUpdate hostdb scan quanity/sleep time #2081
Conversation
S-anasol
changed the title from
Update scan quanity/sleep time
to
Update hostdb scan quanity/sleep time
Jul 5, 2017
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
S-anasol
Jul 7, 2017
Contributor
Actually problem is that scan doesnt cover DB size and every scan get only top N hosts.
Sia/modules/renter/hostdb/scan.go
Line 304 in ec3fbc0
So in this moment we have some good hosts that actually online and work, but not scanned due quanity limit.
|
Actually problem is that scan doesnt cover DB size and every scan get only top N hosts. Sia/modules/renter/hostdb/scan.go Line 304 in ec3fbc0 So in this moment we have some good hosts that actually online and work, but not scanned due quanity limit. |
| @@ -39,15 +39,15 @@ var ( | ||
| // hostCheckupQuantity specifies the number of hosts that get scanned every | ||
| // time there is a regular scanning operation. | ||
| hostCheckupQuantity = build.Select(build.Var{ | ||
| Standard: int(200), | ||
| Standard: int(500), |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
S-anasol
Jul 12, 2017
Contributor
actually outdated limit, it will not cover all online hosts already
S-anasol
Jul 12, 2017
Contributor
actually outdated limit, it will not cover all online hosts already
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Cinerar
Jul 18, 2017
I believe this is not the best way to go. (as a temporary fix i think this is ok)
As long as i understand this aproach can leave best host (the one that changed settings recently) with outdated info and almoust never scan it again.
Limiting scanned hosts centralize the network, as long as only best hosts will be regulary rescanned.
I believe that Score of the host can be tied to period of rescan. This way even not so good hosts will be rescanned sooner or later and there will be not so much network overload.
Cinerar
commented
Jul 18, 2017
|
I believe this is not the best way to go. (as a temporary fix i think this is ok) Limiting scanned hosts centralize the network, as long as only best hosts will be regulary rescanned. |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
DavidVorick
Aug 2, 2017
Member
I'm going to go ahead and close this as a pull request, I think a full discussion is needed when searching for better options. At 1000 hosts or so, I think we're above what we should be scanning every block. I like the 200 hosts limit per 8 hours I think, we probably just need a more intelligent way to scan them.
The most important thing is that we're aware of all the hosts that might be interesting to us.
|
I'm going to go ahead and close this as a pull request, I think a full discussion is needed when searching for better options. At 1000 hosts or so, I think we're above what we should be scanning every block. I like the 200 hosts limit per 8 hours I think, we probably just need a more intelligent way to scan them. The most important thing is that we're aware of all the hosts that might be interesting to us. |
S-anasol commentedJul 5, 2017
•
edited
Current default settings cant handle hostdb grow.
So hostdb have a lot outdated data.
Adjusted settings for siahub wallet.
Enough to keep fresh db for now.
After update we have big fall since many hosts not scanned fast/properly due big hostdb.
https://siahub.info/network