OpenKilda is an open-source OpenFlow controller initially designed for use in a global network with high control-plane latency and a heavy emphasis on latency-centric data path optimisation.
Apache License 2.0
78
stars
53
forks
source link
Update readme. Adjust and clean-up java settings #5652
I updated readme and adjusted settings. It worth to mention that there is a recommendation for memory from ELK which we don't do by default, so I put it into the readme.
For storm settings, the wait parameter is a trade-off between speed of taking a new tuple from the queue (that is low latency) vs CPU utilization (that is robust busy waiting: even if there is nothing new in the queue, program still consumes CPU cycles to check it). For our purposes, we don't really need so low latency in most of the topologies by default, so it's better to keep the wait parameter higher. If some topology requires lower latency, it is better to adjust this parameter in the topology settings and leave the global settings as-is.
I updated readme and adjusted settings. It worth to mention that there is a recommendation for memory from ELK which we don't do by default, so I put it into the readme. For storm settings, the wait parameter is a trade-off between speed of taking a new tuple from the queue (that is low latency) vs CPU utilization (that is robust busy waiting: even if there is nothing new in the queue, program still consumes CPU cycles to check it). For our purposes, we don't really need so low latency in most of the topologies by default, so it's better to keep the wait parameter higher. If some topology requires lower latency, it is better to adjust this parameter in the topology settings and leave the global settings as-is.