FlowVisor is a fairly heavy piece of software in its' current implementation and these system requirements should not be taken too lightly - the number of slices, size of the flowspace, and number of datapaths present in your network all contribute to the scaling factors. Only the most trivial of environments can tolerate the minimum system requirements.
Also, the current implementation, while not disk I/O heavy, is sensitive to poor disk throughput in some situations (usually flowspace updates) and as such some VM environments may cause fast-path performance problems if I/O contention is a problem in the underlying hypervisor.
- 4 Cores
- 4 GB java heap size (-Xmx4096M)
- 2 Cores
- 1 GB java heap size (-Xmx1000M)
To change the JVM heap size used by FlowVisor, you need to modify the script which is the
flowvisor executable, usually located in