c.CacheDynamicClient uses default QPS/burst settings and gets throttled

[ncdc]

We should choose a better default (or disable QPS entirely), and possibly make it configurable.

[ncdc]

FYI @p0lyn0mial @stevekuznetsov @sttts

[p0lyn0mial]

I don't think we should disable QPS now. The cache-server is not protected by Priority and Fairness.
More shards will but more load on the cache-server.
It looks like client-side rate limiting is our only option for now.

Not sure what it would take to enable APF on the server.
Now, I'm not even sure we use max-requests-inflight in the cache-server.

[ncdc]

Fair... but let's go with something with more than the default settings?

[p0lyn0mial]

Fair... but let's go with something with more than the default settings?

+1

Should I prep something or leave it to you?

[ncdc]

Up to you 😀

[p0lyn0mial]

OK, I'll prepare a PR. Thanks for reporting!

[p0lyn0mial]

/assign @p0lyn0mial

[kcp-ci-bot]

Issues go stale after 90d of inactivity.
After a furter 30 days, they will turn rotten.
Mark the issue as fresh with /remove-lifecycle stale.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[kcp-ci-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

/lifecycle rotten