Re: [openflowplugin-dev] [openflowjava-dev] Barrier Message Timeout - 500ms - Rational behind the value

2017-02-23 Thread Michal Rehak -X (mirehak - PANTHEON TECHNOLOGIES at Cisco)
Hi Muthukrishnan, right - I was referring to 'Maximum outbound queue depth'. 25600 is not maximum amount of messages in outbound queue - it is just a threshold value and when crossed then automatically a barrier message is added to queue. But the weird thing about this is that the limit for

Re: [openflowplugin-dev] [openflowjava-dev] Barrier Message Timeout - 500ms - Rational behind the value

2017-02-21 Thread Muthukrishnan Thangasamy
Hi Michal , Thank you for your response , I agree with you , I need some clarity on your response Also there is a complementary parameter - amount of messages in outbound queue without barrier inside. The more messages kept in queue the higher throughput you shall get. Question : My

Re: [openflowplugin-dev] [openflowjava-dev] Barrier Message Timeout - 500ms - Rational behind the value

2017-02-16 Thread Michal Rehak -X (mirehak - PANTHEON TECHNOLOGIES at Cisco)
Hi Muthukrishnan, there is no golden standard behind this value. Setting it to 100ms or even lower value will result into low latency system but this also decreases throughput of system. If you have few switches and little no big requirement on flows per second throughput then 100ms might