Kai, Please take a look at https://issues.apache.org/jira/browse/DISPATCH-781 for insight into how link capacity is used for end-to-end flow control and a prototyped new way to use it.
A quick summary is that synchronizing credit across a network is impractical at scale. Instead, we use link capacity to establish local credit loops (between endpoint and connected router) and then use delivery settlement as the control for end-to-end flow control (and load balancing). maxFrameSize and maxSessionFrames are for session flow control and are completely unrelated to link/credit flow control. linkCapacity is therefore not related to maxFrameSize/maxSessionFrames. -Ted On Fri, Jul 21, 2017 at 10:27 AM, Hudalla Kai (INST/ECS4) < kai.huda...@bosch-si.com> wrote: > Hi, > > I am wondering what the (practical) meaning of the "linkCapacity" > configuration property on listeners is and in particular, how it is related > to the "maxFrameSize" and "maxSessionFrames" properties. Do the latter ones > pose a limit on the former one? My experience is that if I do not specify > any value for "linkCapacity" then the Dispatch Router flows 250 credits to > a sender link connecting to it (assuming that a consumer has connected with > a receiver link interested in the relevant address). This number, however, > seems to be unrelated to the number of credits the consumer has flowed to > Dispatch Router, which lets me assume that the credits to flow to a sender > are mainly related to, well, what exactly? > > Can somebody shed some light on this? > > Mit freundlichen Grüßen / Best regards > > Kai Hudalla > Chief Software Architect > > Bosch Software Innovations GmbH > Schöneberger Ufer 89-91 > 10785 Berlin > GERMANY > www.bosch-si.com > > Registered office: Berlin, Register court: Amtsgericht Charlottenburg, HRB > 148411 B; > Executives: Dr.-Ing. Rainer Kallenbach, Michael Hahn > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org > For additional commands, e-mail: users-h...@qpid.apache.org > >
