You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, I believe our auditing is effectively single threaded, aka, we only ever hit our connected portal node (trin) with a single running content lookup. Since content lookups can take a bit of time due to needing to traverse the network, we should probably run multiple of these concurrently.
How can it be fixed
Change glados-audit to be able to run multiple lookups concurrently.
Add a new flag to glados-audit such as --concurrency N which sets the number of concurrent lookups that can be running at any given time.
The text was updated successfully, but these errors were encountered:
What is wrong
Currently, I believe our auditing is effectively single threaded, aka, we only ever hit our connected portal node (
trin
) with a single running content lookup. Since content lookups can take a bit of time due to needing to traverse the network, we should probably run multiple of these concurrently.How can it be fixed
Change
glados-audit
to be able to run multiple lookups concurrently.Add a new flag to
glados-audit
such as--concurrency N
which sets the number of concurrent lookups that can be running at any given time.The text was updated successfully, but these errors were encountered: