openssl speed -elapsed -evp aes-128-gcm
结果
kvm
You have chosen to measure elapsed time instead of user CPU time.
Doing aes-128-gcm for 3s on 16 size blocks: 14437624 aes-128-gcm's in 3.00s
Doing aes-128-gcm for 3s on 64 size blocks: 4532836 aes-128-gcm's in 3.01s
Doing aes-128-gcm for 3s on 256 size blocks: 1112765 aes-128-gcm's in 3.00s
Doing aes-128-gcm for 3s on 1024 size blocks: 309334 aes-128-gcm's in 3.00s
Doing aes-128-gcm for 3s on 8192 size blocks: 39058 aes-128-gcm's in 3.00s
Doing aes-128-gcm for 3s on 16384 size blocks: 19514 aes-128-gcm's in 3.00s
OpenSSL 1.1.1d 10 Sep 2019
built on: Mon Apr 20 20:23:01 2020 UTC
options:bn(64,64) rc4(8x,char) des(int) aes(partial) blowfish(ptr)
compiler: gcc -fPIC -pthread -m64 -Wa,--noexecstack -Wall -Wa,--noexecstack -g -O2 -fdebug-prefix-map=/build/openssl-8Ocme2/openssl-1.1.1d=. -fstack-protector-strong -Wformat -Werror=format-security -DOPENSSL_USE_NODELETE -DL_ENDIAN -DOPENSSL_PIC -DOPENSSL_CPUID_OBJ -DOPENSSL_IA32_SSE2 -DOPENSSL_BN_ASM_MONT -DOPENSSL_BN_ASM_MONT5 -DOPENSSL_BN_ASM_GF2m -DSHA1_ASM -DSHA256_ASM -DSHA512_ASM -DKECCAK1600_ASM -DRC4_ASM -DMD5_ASM -DAESNI_ASM -DVPAES_ASM -DGHASH_ASM -DECP_NISTZ256_ASM -DX25519_ASM -DPOLY1305_ASM -DNDEBUG -Wdate-time -D_FORTIFY_SOURCE=2
The 'numbers' are in 1000s of bytes per second processed.
type 16 bytes 64 bytes256 bytes 1024 bytes 8192 bytes 16384 bytes
aes-128-gcm 77000.66k96379.24k94955.95k 105586.01k 106654.38k 106572.46k
host
You have chosen to measure elapsed time instead of user CPU time.
Doing aes-128-gcm for 3s on 16 size blocks: 24164323 aes-128-gcm's in 3.00s
Doing aes-128-gcm for 3s on 64 size blocks: 7980988 aes-128-gcm's in 3.00s
Doing aes-128-gcm for 3s on 256 size blocks: 2270894 aes-128-gcm's in 3.00s
Doing aes-128-gcm for 3s on 1024 size blocks: 543897 aes-128-gcm's in 3.00s
Doing aes-128-gcm for 3s on 8192 size blocks: 72932 aes-128-gcm's in 3.00s
Doing aes-128-gcm for 3s on 16384 size blocks: 37819 aes-128-gcm's in 3.00s
OpenSSL 1.1.1d 10 Sep 2019
built on: Mon Apr 20 20:23:01 2020 UTC
options:bn(64,64) rc4(16x,int) des(int) aes(partial) blowfish(ptr)
compiler: gcc -fPIC -pthread -m64 -Wa,--noexecstack -Wall -Wa,--noexecstack -g -O2 -fdebug-prefix-map=/build/openssl-8Ocme2/openssl-1.1.1d=. -fstack-protector-strong -Wformat -Werror=format-security -DOPENSSL_USE_NODELETE -DL_ENDIAN -DOPENSSL_PIC -DOPENSSL_CPUID_OBJ -DOPENSSL_IA32_SSE2 -DOPENSSL_BN_ASM_MONT -DOPENSSL_BN_ASM_MONT5 -DOPENSSL_BN_ASM_GF2m -DSHA1_ASM -DSHA256_ASM -DSHA512_ASM -DKECCAK1600_ASM -DRC4_ASM -DMD5_ASM -DAESNI_ASM -DVPAES_ASM -DGHASH_ASM -DECP_NISTZ256_ASM -DX25519_ASM -DPOLY1305_ASM -DNDEBUG -Wdate-time -D_FORTIFY_SOURCE=2
The 'numbers' are in 1000s of bytes per second processed.
type 16 bytes 64 bytes256 bytes 1024 bytes 8192 bytes 16384 bytes
aes-128-gcm 128876.39k 170261.08k 193782.95k 185650.18k 199152.98k 206542.17k
结论
host比kvm高近一倍
RedHat/CentOS6.2 x86系统KVM虚拟机网络配置 http://www.linuxidc.com/Linux/2012-05/61445.htm作业环境
操作系统:CentOS 6.3 final x86_64
IP: 133.133.10.50
Hostname:myKVM
KVM:qemu-kvm-0.12.1.2-2.295.el6_3.2.x86_64
客户端:Ubuntu和Win7,先在服务器端装好VNC,通过VNC连接服务器CentOS
一、安装KVM及相关软件
1、KVM 需要有 CPU 的支持(Intel vmx 或 AMD svm),在安装 KVM 之前检查一下 CPU 是否提供了虚拟技术的支持:
[root@myKVM ~]# egrep '^flags.*(vmx|svm)' /proc/cpuinfo
有显示, 有显示则说明处理器具有VT功能
2、在主板BIOS中开启CPU的Virtual Technolege(VT,虚化技术)
3、安装kvm及其需要的软件包
[root@myKVM ~]# yum install kvm kmod-kvm qemu kvm-qemu-img virt-viewer virt-manager libvirt libvirt-python python-virtinst
或
[root@myKVM ~]# yum groupinstall KVM
4、检查kvm模块是否安装,使用以下命令显示两个模块则表示安装完成
[root@myKVM ~]# lsmod | grep kvm
kvm_intel 52570 0
kvm 314739 1 kvm_intel
二、启动virt-manager管理界面
1、客户端
VNC到服务器端,因为需要用服务器的图形界面
2、服务器端
启动libvirtd服务,并保证下次自动启动
[root@myKVM ~]# service libvirtd start
Starting libvirtd daemon: [ 确定 ]
[root@myKVM ~]# chkconfig libvirtd on
三、远程创建和管理KVM虚拟机
1. 打开Application=>System Tools =>Virtual Machine Manager就可以装虚拟机了,功能跟VMware类似
2. “Details”中可查看或修改Guest OS的配置信息
3、安装完成后需要将默认的IDE硬盘和网卡换成virtio,并打上驱动程序,这样性能就可以得到提升。(默认好像就是这样的)
欢迎分享,转载请注明来源:夏雨云
评论列表(0条)