From my first mail:
ubuntu VM:
iperf -c 192.168.122.20 -t10
------------------------------------------------------------
Client connecting to 192.168.122.20, TCP port 5001
TCP window size: 85.0 KByte (default)
------------------------------------------------------------
[ 3] local 192.168.122.1 port 52674 connected with 192.168.122.20 port 5001
[ ID] Interval Transfer Bandwidth
[ 3] 0.0-10.0 sec 52.9 GBytes 45.4 Gbits/sec
top:
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
4401 qemu 20 0 6038648 2.309g 22968 S 100.0 7.4 43:24.27
qemu-system-x86
4422 root 20 0 0 0 0 R 83.2 0.0 0:22.90 vhost-4401
24759 justin_+ 20 0 165812 1892 1728 S 51.5 0.0 0:03.91 iperf
I left the -P (number of parallel client threads to run) at default
value - which is 1.
KVM VM used 100% (1 whole cpu core), and the corresponding vhost process
used 80% of CPU core.
So I did run test in single-thread mode for both Linux VM and MirageOS.
On XEN, xentop also showed 100% cpu usage for the MirageOS VM.
Thank you for answering
Justin
On 10/24/2017 02:30 PM, Takayuki Imada wrote:
Hi,
This is similar to what I observed previously, not so surprising.
But, I want you to check how many CPU cores are totally utilized on
both the Linux VM and MirageOS configurations.
I guess only 1 CPU core are utilized on the MirageOS configuration
whereas multiple CPU cores are utilized on the Linux configuration.
Kind regards,
_______________________________________________
MirageOS-devel mailing list
[email protected]
https://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel
