Re: New message count for Openflow Java in ODL master (Boron)
Michal Polkoráb <michal.polkorab@...>
Hi Chinmay,
your point makes sense. However, we should thoroughly consider removing these counters. These were introduced in the past to check if / where there are messages being lost between openflowplugin & openflowjava + to verify the backpressure mechanism. If
we similar issue appears again, these counters might be handy.
Michal From: Chinmay.Mohanta <mohanta.chinmay@...>
Sent: 12 May 2016 13:27 To: Michal Polkoráb Cc: openflowjava-dev@...; shuva.jyoti.kar@...; chinmay.kumar.mohanta@...; ashutosh.bisht@...; muthukumaran.k@... Subject: Re: [openflowjava-dev] New message count for Openflow Java in ODL master (Boron) Hi Michal,
Thanks for your reply.
Indeed the formula indicated by you gives the expected value !!
So it obviates the implementation of a new counter.
However following new thoughts emerge.
Do we really need the counts DS_ENTERED_OFJAVA and DS_ENCODE_SUCCESS ?
Maintaining these two counts (for every message) is costly in terms of performance (due to need for synchronization).
I think we should have counts only for the error scenarios resulting least influence on the performance.
BTW, my goal is to simplify the debugging process to find out whenever/wherever there is a message drop due to resource contention. Message drop count will provide an essential input to rationalize the provisioning of resources.
Thanks and Regards,
Chinmay @ ericsson
On Wed, May 11, 2016 at 5:22 PM, Michal Polkoráb
<michal.polkorab@...> wrote:
MichalPolkoráb Software Engineer
|