Difference between revisions of "Solarflare SFN7122F"

From Define Wiki
Jump to navigation Jump to search
Line 40: Line 40:
 
|-
 
|-
 
|Onload best latency || 97869.02
 
|Onload best latency || 97869.02
 +
|-
 +
|}
 +
 +
== Iperf Results ==
 +
 +
===Serial Runs ===
 +
 +
{| class="wikitable" style="text-align: center;"
 +
|- Test || Threads || Bandwidth
 +
|-
 +
|Iperf || 1 || 9.42
 +
|-
 +
|Onload iperf|| 1 ||  9.41
 +
|-
 +
|Onload best latency || 1 || 9.41
 +
|-
 +
|}
 +
 +
=== Parallel Runs ===
 +
 +
{| class="wikitable" style="text-align: center;"
 +
|- Test || Threads || Bandwidth
 +
|-
 +
|Iperf || 10 || 9.42
 +
|-
 +
|Onload iperf|| 10 ||  9.41
 +
|-
 +
|Onload best latency || 10 || 9.41
 
|-
 
|-
 
|}
 
|}

Revision as of 12:29, 21 August 2013

Onload Install

System requierments

  • Centos with full updates
  • Development tools

Installation

scripts/onload_install
onload_tool reload

Netperf Tests

To accelerate an application with the Onload user-level transport, simply invoke the application on the command line as normal, prepended with "onload".

ie. Instead of:

  netperf -t TCP_RR -H myserver

do this:

  onload netperf -t TCP_RR -H myserver

and tuned for best latency:

  onload -p latency netperf -t TCP_RR -H myserver


Netperf Results

Netperf 12,333.00
Onload Netperf 68004.42
Onload best latency 97869.02

Iperf Results

Serial Runs

Iperf 1 9.42
Onload iperf 1 9.41
Onload best latency 1 9.41

Parallel Runs

Iperf 10 9.42
Onload iperf 10 9.41
Onload best latency 10 9.41