Gus Eggert

Actually I'm going to close this as this was really just a subtask for https://github.com/ipfs/go-bitswap/issues/564 and it doesn't hold any useful context if this issue comes up again in the...

Splitting server and client: https://github.com/ipfs/go-bitswap/issues/568

Since the server is simpler to implement than the client, I'm starting with the server. I'm also holding Testground tests as a hard requirement for measuring performance. After that, I...

Any way to get this merged, @lunaryorn @fmdkdd ?

What is actionable here? What is the expected behavior?

The hydras definitely need a clear SLI metric...currently we can't tell how well the hydras are doing wrt the whole network. This also means from an operational perspective that it's...

So the logs originally showed the timeouts were due to a timeout while reading the response body: ``` 2022-08-14T09:37:46.803Z ERROR service/client/delegatedrouting proto/proto_edelweiss.go:1234 client received error response (context deadline exceeded (Client.Timeout...

I've integrated Resource Manager, added RM metrics, added them to the dashboard, and tweaked the RM limits to be low enough to throttle spikes but to generally allow most traffic....

1) is done. I did 2) a couple weeks ago, see https://github.com/ipfs/specs/commit/0b123fa5c3ddf126f55bcec2aa67b2b91247d959 3) done in https://github.com/libp2p/hydra-booster/commit/6967a65c3f6945c40a6cc1ac8d378bbf173e539d 4) done in https://github.com/libp2p/hydra-booster/commit/d48d8984c19c125c55c199a5e790bed93d9ed2b7

Update: last week I deployed Reframe to the full Hydra fleet, but almost all reqs started timing out so I rolled it back. Have been debugging w/ @masih in between...