This group is locked. No changes can be made to the group while it is locked.
- New message count for Openflow Java in ODL master (Boron)
Re: New message count for Openflow Java in ODL master (Boron)
toggle quoted messageShow quoted text
Hi Michal and all,
In that case I think best would be to introduce the functionality that would allow to enable/disable (via JMX or Config subsys) the counter module on demand.
In this way we can have the message counts when we need it otherwise count collection can be turned off.
Thanks and Regards,
Chinmay @ Ericsson
On Fri, May 13, 2016 at 3:37 PM, Michal Polkoráb <michal.polkorab@...>
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.
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
Sídlo / Mlynské
Nivy 56 /
821 05 Bratislava
R&D centrum / Janka Kráľa 9 /
974 01 Banská Bystrica / Slovakia
+421 918 378 907 /
reception: +421 2 206 65 114
Join firstname.lastname@example.org to automatically receive all group messages.