[
https://issues.apache.org/jira/browse/DISPATCH-2007?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17310622#comment-17310622
]
Robbie Gemmell commented on DISPATCH-2007:
------------------------------------------
The tradeoff with the alternative approach being that if you are limiting the
session window to e.g govern memory usage, then by having lots of sessions
instead of a smaller number, you would need to proportionally lower all the
individual session windows to govern overall usage to similar extent, perhaps
leaving you with either smaller than desirable windows or less governed limit.
You will also still need to appropriately mux the session traffic to avoid
largely the same issue arising similarly one level up on the connection itself.
Multiple links on a session can be interleaved at the transfer frame level, to
help avoid one link on the session starving all the rest entirely. Proton-J
does this to a far greater extent than Proton-C can currently, due to
differences in the way they generate frames (one-transfer-per-message at a
time, vs as-many-transfers-as-possible).
> Need better allocation of sessions across inter-router links
> ------------------------------------------------------------
>
> Key: DISPATCH-2007
> URL: https://issues.apache.org/jira/browse/DISPATCH-2007
> Project: Qpid Dispatch
> Issue Type: Improvement
> Components: Router Node
> Affects Versions: 1.15.0
> Reporter: Ken Giusti
> Assignee: Ken Giusti
> Priority: Major
> Fix For: 1.16.0
>
>
> Inter-router connections establish several links for passing traffic between
> routers. Session allocation across the links is currently:
> * one session dedicated to both router control links
> * one session for EACH priority link pair (in/out) - 10 sessions total
> * one session used by all link route links
> * one session used by all streaming link
> There is an issue with sharing the session in the case of streaming & link
> routes. Due to the way session flow control works all links on the session
> share bandwidth. This means one slow link can force flow control on all of
> its peer links on the session.
> Proton allows for at most 32K sessions per connection. We should make an
> attempt to use dedicated sessions for link route and streaming links, sharing
> only when the number of link route + streaming links exceeds the proton
> limit.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
