Enrico Rotundo

Public dashboard: https://protocollabs.grafana.net/public-dashboards/9fe7717277e540a7be88f1e8e8339bd8?orgId=1

**Update:** still busy configuring the Grafana dashboard to display the actual total sum of the metrics. These are counters and they do reset every now and then, so a simple...

**Update:** As per [this thread](https://filecoinproject.slack.com/archives/C02RLM3JHUY/p1662641530301679?thread_ts=1662474839.802219&cid=C02RLM3JHUY), I've switched to using `irate` Public link: https://protocollabs.grafana.net/public-dashboards/9fe7717277e540a7be88f1e8e8339bd8 Private link (for editing): https://protocollabs.grafana.net/d/x6I6OcG4z/bacalhau?orgId=1&from=now-7d&to=now --- Follow up issue: https://github.com/filecoin-project/bacalhau/issues/582 (Add more metrics to the codebase).

Note Grafana cloud public dashboards have only alpha support - sometimes it's quite painful to have the public synced with the private dashboard :(

Related to: https://github.com/filecoin-project/bacalhau/issues/494

Taking one step back here 🤔. Is the final goal saving user's time by sparing them the `ipfs add` step (e.g. `cid=$(ipfs add --quiet ./testdata/grep_file.txt)`)? If that's the case, why...

### Some quick initial findings It's already linear: ``` bacalhau list --wide --number 1 0.39s user 0.06s system 26% cpu 1.681 total bacalhau list --wide --number 10 0.50s user 0.14s...

I see two points here: * The `/list` endpoint (`requestinglistfromserver` below) returns **all** jobs on the backend. There's no filtering. We need a more scalable approach there. * There're multitude...

Moving this issue to #611

How to reproduce this? 🤔