[Xen-users] Halsign 1.1

[jim burns <jim_burn@xxxxxxxxxxxxx>]

Reviewing the new Halsign release. The package name has changed from 
GateKeeper 1.0 to TurboGate 1.1. 1.1 does *not* uninstall 1.0 - do that 
first. And make sure the pv nic is not running - boot w/o /pv and disable the 
Halsign adapter and enable the Realtek (Netfront) one, as uninstalling 1.0 
will remove the Halsign adapter. While the linux tarball still has the GPL 
COPYING file, the Windows .exe license screen has removed all references to 
GPL components.

Ok, here are my iometer and iperf results.

Equipment: core duo 2300, 1.66ghz each, sata drive configured for UDMA/100
System: fc8 32bit pae, xen 3.1.2, xen.gz 3.1.0-rc7, dom0 2.6.21
Tested hvm: XP Pro SP2, 2002, tested w/ iometer 2006-07-27 (1Gb \iobw.tst, 
5min run) & iperf 1.7.0 (1 min run)

Previous iometer results with 1.0 (from the 'New binary release of GPL PV 
drivers for Windows' thread on 02/24):

pattern 4k, 50% read, 0% random

(dynamo is the windows or linux client doing the actual work)
dynamo on?  |   io/s   |  MB/s  | Avg. i/o time(ms} | max i/o time(ms) | %CPU
domu w/hals.|   331.3  |   1.29 |      -31.78       |       0          | 39.02
domu w/qemu |   460.2  |   1.80 |       -5.85       |       0          | 42.35
dom0 w/4Gb  |   958.1  |   3.75 |        1.04       |      187.8       |  0
dom0 w/4Gb  |  1080.5  |   4.22 |        0.92       |      192.2       |  0
(2nd dom0 numbers from when booted w/o /pv)

pattern 32k, 50% read, 0% random

domu w/hals.|    81.1  |   2.53 |       49.94       |        0         | 36.36
domu w/qemu |    74.6  |   2.33 |       10.11       |        0         | 32.00
dom0 w/4Gb  |   138.9  |   4.34 |        7.20       |      340.8       |  0
dom0 w/4Gb  |   148.0  |   4.62 |        6.76       |      228.6       |  0

And now the 1.1 results:

pattern 4k, 50% read, 0% random

dynamo on?  |   io/s   |  MB/s  | Avg. i/o time(ms} | max i/o time(ms) | %CPU
domu w/hals.|   226.7  |   0.89 |        5.25       |       0          | 48.57
domu w/qemu |   233.4  |   0.91 |       -8.42       |       0          | 42.23
dom0 w/4Gb  |   873.7  |   3.41 |        1.14       |      221.5       |  0
dom0 w/4Gb  |  1118.0  |   4.37 |        0.89       |      181.3       |  0
(2nd dom0 numbers from when booted w/o /pv)

pattern 32k, 50% read, 0% random

domu w/hals.|    73.4  |   2.29 |       54.35       |        0         | 45.21
domu w/qemu |    72.2  |   2.26 |      201.02       |        0         | 48.06
dom0 w/4Gb  |   140.5  |   4.39 |        7.11       |      254.2       |  0
dom0 w/4Gb  |   139.2  |   4.35 |        7.18       |      263.0       |  0

The numbers are negligibly different between the two domu drivers, and 1.1 is 
somewhat worse than 1.0. While the 32k pattern numbers are better, they are 
not as good as dom0, probably because my Halsign domu is on a samba mount, 
unlike my gplpv domu, which is on the local disk.

And now the iperf results. Since I didn't have iperf at the time I ran my 
original gplpv tests (from the 'Release 0.8.0 of GPL PV Drivers for Windows' 
thread on 03/01), there are no old results to compare against:

Server/listener on dom0, client on domu. In the table below, 'udp Mpbs' is the 
observed, and '-b Mpbs' is the requested rate. (The server has to be invoked 
with 'iperf -s -u' for udp tests.)

machine  | tcp Mbps| udp Mbps| -b Mbps | udp packet loss
halsign  |     16.2|      0.1|       1 |   0.0%
realtek  |      9.8|      3.8|      10 |   0.0%

The Halsign driver is 65% faster. (Gplpv 0.8.4 was about 2x faster.)

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users