[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: AW: [amqp] Size-based link flow control
The session flow control has frame-size resolution and we also use that to cap memory use in the gateway.
The links end up interacting with the respective link targetâs backend processor/storage. We do have the scenario where a single inbound session carries a bundle of links where each
link talks to a different backend. For that, the team wants finer grained flow control metric than a message count.
Von: Alan Conway <aconway@redhat.com>
Qpid Dispatch uses the existing byte-based session flow control to bound its memory use. It does effectively block clients that send a lot of bytes - regardless of whether it is many small messages or some very
large ones. Why do you need a per-link limit on top of that? A per-link limit allows senders that create a ton of links to blow up the receiver. Of course a malicious sender could create a ton of sessions, but that's much less likely to happen by accident, and the max number
of sessions is easy to limit giving you a guaranteed upper-bound on memory per connection. On Fri, Mar 8, 2019 at 2:34 PM Clemens Vasters <clemensv@microsoft.com> wrote:
|
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]