Create a benchmark tool for contributor
zosorock opened this issue · comments
So we can accurately access if they can contribute in a timely manner. Suggestion is to add the tool to the generate function so it will only generate a key if it can meet the requirements. The measurement would then be added to the key and posted to the Coordinator on first contact.
I tried to run the reliability score and it just exited after the 3rd message. No error, nothing:
Aug 18 00:20:53.218 INFO setup1_contributor::commands::contribute: Checking reliability score before joining the queue
Aug 18 00:21:40.598 INFO phase1::initialization: phase1-initialization complete
Aug 18 00:21:41.414 INFO phase1::computation: starting...
on the Contributor side I can see something but I do not think it is a good result. This was tested from a machine that meets both the computing and the bandwidth requirements:
Aug 18 00:28:50.424 TRACE aleo_setup_coordinator::authentication::authentication_middleware: Authentication for address aleo1n4h36jfhcynlulu8kqfz3lzgz89qz4h6yp4mjt0zajgm376afqrsspf0km message is: "get /v1/contributor/reliability"
Aug 18 00:29:37.697 INFO aleo_setup_coordinator::reliability::measurements::bandwidth: Bandwidth measured with 100Mb of data, time passed 45676ms
Aug 18 00:29:52.308 INFO aleo_setup_coordinator::api::contributor::reliability: Reliability successfully measured for a contributor aleo1n4h36jfhcynlulu8kqfz3lzgz89qz4h6yp4mjt0zajgm376afqrsspf0km.contributor with the result 2
Aug 18 00:29:52.470 TRACE aleo_setup_coordinator::api::queue::contributor: Contributor aleo1n4h36jfhcynlulu8kqfz3lzgz89qz4h6yp4mjt0zajgm376afqrsspf0km.contributor doesn't have enough reliability score. Required 8, but got 2
@zosorock is it solved by the docker container which you've made?
closed in favor of reliability checks by coordinator and Docker benchmarker