-
Notifications
You must be signed in to change notification settings - Fork 1
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
Issues with pinging rounds #17
Comments
In that case, you would have to check the publication time of those CIDs. The hoarder gets the next ping time from using the As we already mentioned it before, the current code is not 100% ready for Asynchronously track new CIDs. In this case, the hoarder seems to be filling all the |
Exactly. So that would constitute adding a |
the |
I have noticed some issues with running experiments using the
JSON FILE
approach and theHTTP SERVER
Json file getting way more pings than hours elapsed
I'm running an instance of the hoarder using this configuration:
ipfs-cid-hoarder run --database-endpoint "user=postgres password=postgres database=optimistic_provide host=localhost port=5432 sslmode=disable" --req-interval 30m --study-duration 48h --already-published-cids true --cid-file providersen.json --cid-source "json-file" --log-level debug > logs_op.txt
The output of the log file seems to indicate that the hoarder pings way more than it should:
While the elapsed time is around 8 hours.
HTTP server pings way less than expected
I'm running an instance of the hoarder using this configuration:
ipfs-cid-hoarder run --database-endpoint "user=postgres password=postgres database=optimistic_provide host=localhost port=5432 sslmode=disable" --req-interval 30m --study-duration 48h --already-published-cids true --cid-source "http-server" --log-level debug > logs_op.txt
The output of the log file seems to indicate that the hoarder pings way less than it should:
The hoarder has finished the study.
The text was updated successfully, but these errors were encountered: