From Wanos Wiki
Jump to: navigation, search
 
Line 1: Line 1:
<font size=5> Document migrated. An updated [http://wanos.co/docs/docs/wanos-admin-guide/configuration/optimization-levels/ Optimization Levels Guide] can be found in the http://wanos.co/docs Wanos Documentation site] </font>
+
<font size=5> Document migrated. An updated [http://wanos.co/docs/docs/wanos-admin-guide/configuration/optimization-levels/ Optimization Levels Guide] can be found in the [http://wanos.co/docs Wanos Documentation site] </font>
 
<font color=#dddddd>
 
<font color=#dddddd>
  

Latest revision as of 18:40, 10 February 2017

Document migrated. An updated Optimization Levels Guide can be found in the Wanos Documentation site

  • Compression Level

Level 3 for best results. Level 0 to disable. Higher Compression levels will generally provider better compression ratio at the cost of extra CPU cycles. Lower Compression levels will provider lower ratios, but provide higher throughput.

  • Deduplication Level

Level 4 for best results. Level 0 for receive only. Higher levels provide the best ratios while lower levels provide more throughput. Level 0 accepts deduplicated traffic but does not apply deduplication towards the remote peer. This option is for high speed or resource limited scenarios.

  • Encapsulation

For optimized traffic, Encapsulation needs to match on all sites. IPComp is the most efficient, but may not be compatible with intermediate NAT devices. UDP is more lenient to NAT and Firewall devices but carry extra overhead per packet.

  • Global Wan Tx Rate

The Global WAN Outbound Tx Shaper. Values are in kbps. Default is 0. 0 means Disabled. The Global Shaper will limit all outbound traffic to the target rate. This is useful in scenarios where peak WAN speeds have a cost implication. The Global rate is also used where congestion in the WAN affect Packet Loss Recovery. In these scenarios it is recommended to set the WAN speed.

  • Packet Loss Recovery

Level 1 - Most conservative loss detection and recovery. Level 4 - Most aggressive loss detection and recovery. Conservative PLR means Wanos will wait longer and generate less PLR traffic. Aggressive Loss detection means Wanos will try to recover from loss earlier. TCP Acceleration would typically be higher on more aggressive settings.

  • Peer Timeout (value in seconds)

Controls how long to wait before considering a peer down. Traffic for this peer will switch to bypass until the next peer hello packet is received. Ready peers move to up state instantly as soon as the first tagged TCP SYN packet is received. A peer timeout of 10 seconds will cause Wanos to move to the bypass state sooner. A peer timeout of 120 seconds will ensure Wanos waits 2 minutes before considering the peer to be down and move the traffic to pass-through.