sys_logo

Всем привет! Публикую тесты нескольких серверов от OVH которые я провел в октябре этого года. Все серверы для теста любезно предоставил alice2k

На сей раз у нас на тесте вот такой сервер: http://www.soyoustart.com/ie/offers/game-1.xml

Уже из названия понятно что это игровой сервер. Здесь процессор Intel i7 4790K, 16 Gb RAM и SSD на 120Gb. Для хостинга этот сервер не совсем пригоден, а вот для игр скорее всего в самый раз.

Начнем тест.

Информация о сервере

Спецификация сервера:

Стоит такая конфигурация сейчас 49.99 евро. Стоит также отметить что здесь есть возможность покупки дополнительных IP (об этом в отдельном посте) и есть встроенный антиддос заточенный специально под игровые сервера.

На тесте сервер с CentOS 6.6

[root@ns30093xx ~]# cat /etc/issue
CentOS release 6.6 (Final)
Linux ns30093xx.ip-151-80-108.eu 3.14.32-xxxx-grs-ipv6-64 #5 SMP Wed Sep 9 17:24:34 CEST 2015 x86_64 x86_64 x86_64 GNU/Linux

server    : 581799
hostname  : ns30093xx.ip-151-80-108.eu
eth0 IPv4 : 151.80.108.xx
eth0 IPv6 : 2001:41d0:d:1c51::/64

CPU и RAM

[root@ns30093xx ~]# cat /proc/cpuinfo
processor    : 0
vendor_id    : GenuineIntel
cpu family    : 6
model        : 60
model name    : Intel(R) Core(TM) i7-4790K CPU @ 4.00GHz
stepping    : 3
microcode    : 0x19
cpu MHz        : 4000.000
cache size    : 8192 KB
physical id    : 0
siblings    : 8
core id        : 0
cpu cores    : 4
apicid        : 0
initial apicid    : 0
fpu        : yes
fpu_exception    : yes
cpuid level    : 13
wp        : yes
flags        : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf eagerfpu pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 fma cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm ida arat epb xsaveopt pln pts dtherm tpr_shadow vnmi flexpriority ept vpid fsgsbase tsc_adjust bmi1 hle avx2 smep bmi2 erms invpcid rtm
bogomips    : 7981.41
clflush size    : 64
cache_alignment    : 64
address sizes    : 39 bits physical, 48 bits virtual
power management:

...

processor    : 7
vendor_id    : GenuineIntel
cpu family    : 6
model        : 60
model name    : Intel(R) Core(TM) i7-4790K CPU @ 4.00GHz
stepping    : 3
microcode    : 0x19
cpu MHz        : 1615.312
cache size    : 8192 KB
physical id    : 0
siblings    : 8
core id        : 3
cpu cores    : 4
apicid        : 7
initial apicid    : 7
fpu        : yes
fpu_exception    : yes
cpuid level    : 13
wp        : yes
flags        : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf eagerfpu pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 fma cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm ida arat epb xsaveopt pln pts dtherm tpr_shadow vnmi flexpriority ept vpid fsgsbase tsc_adjust bmi1 hle avx2 smep bmi2 erms invpcid rtm
bogomips    : 7981.41
clflush size    : 64
cache_alignment    : 64
address sizes    : 39 bits physical, 48 bits virtual
power management:

[root@ns30093xx ~]# cat /proc/meminfo
MemTotal:       16364420 kB
MemFree:        16045652 kB
MemAvailable:   16102972 kB
Buffers:           18768 kB
Cached:            70152 kB
SwapCached:            0 kB
Active:            62444 kB
Inactive:          54244 kB
Active(anon):      27800 kB
Inactive(anon):      260 kB
Active(file):      34644 kB
Inactive(file):    53984 kB
Unevictable:           0 kB
Mlocked:               0 kB
SwapTotal:       2096124 kB
SwapFree:        2096124 kB
Dirty:                 8 kB
Writeback:             0 kB
AnonPages:         27776 kB
Mapped:             8832 kB
Shmem:               292 kB
Slab:              43632 kB
SReclaimable:      18212 kB
SUnreclaim:        25420 kB
KernelStack:        2640 kB
PageTables:         1848 kB
NFS_Unstable:          0 kB
Bounce:                0 kB
WritebackTmp:          0 kB
CommitLimit:    10278332 kB
Committed_AS:     166732 kB
VmallocTotal:   34359738367 kB
VmallocUsed:      105872 kB
VmallocChunk:   34359475372 kB
HardwareCorrupted:     0 kB
DirectMap4k:       11652 kB
DirectMap2M:     4057088 kB
DirectMap1G:    12582912 kB

Диск примонтирован по-умолчанию вот так:

[root@ns30093xx ~]# df -H
Filesystem      Size  Used Avail Use% Mounted on
rootfs          117G  722M  111G   1% /
/dev/root       117G  722M  111G   1% /
devtmpfs        8,4G  295k  8,4G   1% /dev
tmpfs           8,4G     0  8,4G   0% /dev/shm
/dev/root       117G  722M  111G   1% /var/named/chroot/etc/named
/dev/root       117G  722M  111G   1% /var/named/chroot/var/named
/dev/root       117G  722M  111G   1% /var/named/chroot/etc/named.conf
/dev/root       117G  722M  111G   1% /var/named/chroot/etc/named.rfc1912.zones
/dev/root       117G  722M  111G   1% /var/named/chroot/etc/rndc.key
/dev/root       117G  722M  111G   1% /var/named/chroot/usr/lib64/bind
/dev/root       117G  722M  111G   1% /var/named/chroot/etc/named.iscdlv.key
/dev/root       117G  722M  111G   1% /var/named/chroot/etc/named.root.key

Более подробная информация о железе:

[root@ns30093xx ~]# inxi -b
System:    Host: ns30093xx.ip-151-80-108.eu Kernel: 3.14.32-xxxx-grs-ipv6-64 x86_64 (64 bit) Console: tty 0
           Distro: CentOS release 6.7 (Final)
Machine:   System: ASUS product: All Series
           Mobo: ASUSTeK model: H97M-PLUS v: Rev X.0x serial: 141236406600153
           Bios: American Megatrends v: 2404 date: 03/04/2015
CPU:       Quad core Intel Core i7-4790K (-HT-MCP-) speed/max: 3936/4400 MHz
Graphics:  Card: Intel Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller
           Display Server: N/A driver: N/A tty size: 182x31 Advanced Data: N/A for root out of X
Network:   Card: Intel Ethernet Connection (2) I218-V driver: e1000e
Drives:    HDD Total Size: 120.0GB (1.7% used)
Info:      Processes: 147 Uptime: 2:18 Memory: 301.1/15980.9MB Init: Upstart runlevel: 3
           Client: Shell (bash) inxi: 2.2.28

Подробно об установленом SSD:

[root@ns30093xx /]# hdparm -I /dev/sda

/dev/sda:

ATA device, with non-removable media
    Model Number:       SAMSUNG MZ7LM120HCFD-00003              
    Serial Number:      S22PNYAG500258      
    Firmware Revision:  GXT3003Q
    Transport:          Serial, ATA8-AST, SATA 1.0a, SATA II Extensions, SATA Rev 2.5, SATA Rev 2.6, SATA Rev 3.0
Standards:
    Used: unknown (minor revision code 0x0039)
    Supported: 9 8 7 6 5
    Likely used: 9
Configuration:
    Logical        max    current
    cylinders    16383    16383
    heads        16    16
    sectors/track    63    63
    --
    CHS current addressable sectors:   16514064
    LBA    user addressable sectors:  234441648
    LBA48  user addressable sectors:  234441648
    Logical  Sector size:                   512 bytes
    Physical Sector size:                   512 bytes
    Logical Sector-0 offset:                  0 bytes
    device size with M = 1024*1024:      114473 MBytes
    device size with M = 1000*1000:      120034 MBytes (120 GB)
    cache/buffer size  = unknown
    Nominal Media Rotation Rate: Solid State Device
Capabilities:
    LBA, IORDY(can be disabled)
    Queue depth: 32
    Standby timer values: spec'd by Standard, no device specific minimum
    R/W multiple sector transfer: Max = 16    Current = 16
    DMA: mdma0 mdma1 mdma2 udma0 udma1 udma2 udma3 udma4 udma5 *udma6
         Cycle time: min=120ns recommended=120ns
    PIO: pio0 pio1 pio2 pio3 pio4
         Cycle time: no flow control=120ns  IORDY flow control=120ns
Commands/features:
    Enabled    Supported:
       *    SMART feature set
            Security Mode feature set
       *    Power Management feature set
       *    Write cache
       *    Look-ahead
       *    Host Protected Area feature set
       *    WRITE_BUFFER command
       *    READ_BUFFER command
       *    NOP cmd
       *    DOWNLOAD_MICROCODE
            SET_MAX security extension
       *    48-bit Address feature set
       *    Device Configuration Overlay feature set
       *    Mandatory FLUSH_CACHE
       *    FLUSH_CACHE_EXT
       *    SMART error logging
       *    SMART self-test
       *    General Purpose Logging feature set
       *    WRITE_{DMA|MULTIPLE}_FUA_EXT
       *    64-bit World wide name
            Write-Read-Verify feature set
       *    WRITE_UNCORRECTABLE_EXT command
       *    {READ,WRITE}_DMA_EXT_GPL commands
       *    Segmented DOWNLOAD_MICROCODE
       *    Gen1 signaling speed (1.5Gb/s)
       *    Gen2 signaling speed (3.0Gb/s)
       *    Gen3 signaling speed (6.0Gb/s)
       *    Native Command Queueing (NCQ)
       *    Phy event counters
       *    unknown 76[15]
       *    DMA Setup Auto-Activate optimization
       *    Asynchronous notification (eg. media change)
       *    Software settings preservation
       *    SMART Command Transport (SCT) feature set
       *    SCT Write Same (AC2)
       *    SCT Error Recovery Control (AC3)
       *    SCT Features Control (AC4)
       *    SCT Data Tables (AC5)
       *    DOWNLOAD MICROCODE DMA command
       *    SET MAX SETPASSWORD/UNLOCK DMA commands
       *    WRITE BUFFER DMA command
       *    READ BUFFER DMA command
       *    Data Set Management TRIM supported (limit 8 blocks)
       *    Deterministic read ZEROs after TRIM
Security:
    Master password revision code = 65534
        supported
    not    enabled
    not    locked
        frozen
    not    expired: security count
        supported: enhanced erase
    32min for SECURITY ERASE UNIT. 32min for ENHANCED SECURITY ERASE UNIT.
Logical Unit WWN Device Identifier: 5002538c00018294
    NAA        : 5
    IEEE OUI    : 002538
    Unique ID    : c00018294
Checksum: correct

Тесты и замеры производительности

Пинг из Ульяновска:

[rail@localhost ~]$ ping 151.80.108.xx
PING 151.80.108.xx (151.80.108.xx) 56(84) bytes of data.
64 bytes from 151.80.108.xx: icmp_seq=1 ttl=53 time=79.7 ms
64 bytes from 151.80.108.xx: icmp_seq=2 ttl=53 time=79.2 ms
64 bytes from 151.80.108.xx: icmp_seq=3 ttl=53 time=82.4 ms
64 bytes from 151.80.108.xx: icmp_seq=4 ttl=53 time=79.3 ms
64 bytes from 151.80.108.xx: icmp_seq=5 ttl=53 time=79.3 ms
64 bytes from 151.80.108.xx: icmp_seq=6 ttl=53 time=80.3 ms
64 bytes from 151.80.108.xx: icmp_seq=7 ttl=53 time=80.0 ms
64 bytes from 151.80.108.xx: icmp_seq=8 ttl=53 time=79.3 ms
64 bytes from 151.80.108.xx: icmp_seq=9 ttl=53 time=79.3 ms
64 bytes from 151.80.108.xx: icmp_seq=10 ttl=53 time=79.3 ms
64 bytes from 151.80.108.xx: icmp_seq=11 ttl=53 time=82.6 ms
64 bytes from 151.80.108.xx: icmp_seq=12 ttl=53 time=82.9 ms
^C
--- 151.80.108.xx ping statistics ---
12 packets transmitted, 12 received, 0% packet loss, time 11015ms
rtt min/avg/max/mdev = 79.239/80.353/82.921/1.429 ms

SSD что-то не порадовал высокой скоростью записи:

[root@ns30093xx ~]# dd if=/dev/zero of=test bs=64k count=16k conv=fdatasync
16384+0 записей считано
16384+0 записей написано
 скопировано 1073741824 байта (1,1 GB), 8,11755 c, 132 MB/c
[root@ns30093xx ~]# rm test
rm: удалить обычный файл «test»? y
[root@ns30093xx ~]# dd if=/dev/zero of=test bs=64k count=16k conv=fdatasync
16384+0 записей считано
16384+0 записей написано
 скопировано 1073741824 байта (1,1 GB), 8,11956 c, 132 MB/c
[root@ns30093xx ~]# rm test
rm: удалить обычный файл «test»? y       
[root@ns30093xx ~]# dd if=/dev/zero of=test bs=64k count=16k conv=fdatasync
16384+0 записей считано
16384+0 записей написано
 скопировано 1073741824 байта (1,1 GB), 8,09374 c, 133 MB/c

Для сравнения на тарифах EVO от FastVPS этот показатель равен около 500 MB/c

Тесты Sysbench

Замеряем производительность процессора нагружая его вычислениями 64-разрядных чисел. Попробуем запустить вычисление в один поток.

[root@ns30093xx ~]# sysbench --test=cpu --cpu-max-prime=20000 --num-threads=1 run
sysbench 0.4.12:  multi-threaded system evaluation benchmark

Running the test with following options:
Number of threads: 1

Doing CPU performance benchmark

Threads started!
Done.

Maximum prime number checked in CPU test: 20000


Test execution summary:
    total time:                          18.3031s
    total number of events:              10000
    total time taken by event execution: 18.3025
    per-request statistics:
         min:                                  1.81ms
         avg:                                  1.83ms
         max:                                  9.71ms
         approx.  95 percentile:               1.82ms

Threads fairness:
    events (avg/stddev):           10000.0000/0.00
    execution time (avg/stddev):   18.3025/0.00

Теперь запустим 4 потока по числу физических ядер процессора.

[root@ns30093xx ~]# sysbench --test=cpu --cpu-max-prime=20000 --num-threads=4 run
sysbench 0.4.12:  multi-threaded system evaluation benchmark

Running the test with following options:
Number of threads: 4

Doing CPU performance benchmark

Threads started!
Done.

Maximum prime number checked in CPU test: 20000


Test execution summary:
    total time:                          4.7537s
    total number of events:              10000
    total time taken by event execution: 19.0128
    per-request statistics:
         min:                                  1.90ms
         avg:                                  1.90ms
         max:                                  6.04ms
         approx.  95 percentile:               1.90ms

Threads fairness:
    events (avg/stddev):           2500.0000/0.00
    execution time (avg/stddev):   4.7532/0.00

Тестим процессор нагружая его большим количеством конкурирующих потоков:

[root@ns30093xx ~]# sysbench --test=threads --thread-locks=1 --max-time=20s run
sysbench 0.4.12:  multi-threaded system evaluation benchmark

Running the test with following options:
Number of threads: 1

Doing thread subsystem performance test
Thread yields per test: 1000 Locks used: 1
Threads started!
Done.


Test execution summary:
    total time:                          0.9863s
    total number of events:              10000
    total time taken by event execution: 0.9857
    per-request statistics:
         min:                                  0.10ms
         avg:                                  0.10ms
         max:                                  0.13ms
         approx.  95 percentile:               0.10ms

Threads fairness:
    events (avg/stddev):           10000.0000/0.00
    execution time (avg/stddev):   0.9857/0.00
[root@ns30093xx ~]# sysbench --test=mutex --num-threads=64 run
sysbench 0.4.12:  multi-threaded system evaluation benchmark

Running the test with following options:
Number of threads: 64

Doing mutex performance test
Threads started!
Done.


Test execution summary:
    total time:                          0.6210s
    total number of events:              64
    total time taken by event execution: 38.9916
    per-request statistics:
         min:                                593.22ms
         avg:                                609.24ms
         max:                                620.56ms
         approx.  95 percentile:             620.17ms

Threads fairness:
    events (avg/stddev):           1.0000/0.00
    execution time (avg/stddev):   0.6092/0.01

Теперь замерим производительность оперативной памяти:

[root@ns30093xx ~]# sysbench --test=memory --memory-total-size=16G --num-threads=4 run
sysbench 0.4.12:  multi-threaded system evaluation benchmark

Running the test with following options:
Number of threads: 4

Doing memory operations speed test
Memory block size: 1K

Memory transfer size: 16384M

Memory operations type: write
Memory scope type: global
Threads started!
Done.

Operations performed: 16777216 (6357461.09 ops/sec)

16384.00 MB transferred (6208.46 MB/sec)


Test execution summary:
    total time:                          2.6390s
    total number of events:              16777216
    total time taken by event execution: 6.5592
    per-request statistics:
         min:                                  0.00ms
         avg:                                  0.00ms
         max:                                  0.06ms
         approx.  95 percentile:               0.00ms

Threads fairness:
    events (avg/stddev):           4194304.0000/264294.79
    execution time (avg/stddev):   1.6398/0.02

Тест скорости чтения и записи на диск. Чтобы на тест не влиял кэш в ОЗУ зададим общий объем тестовых чуть больше чем установлено на сервере RAM.

[root@ns30093xx ~]# sysbench --test=fileio --file-total-size=20G prepare
sysbench 0.4.12:  multi-threaded system evaluation benchmark

128 files, 163840Kb each, 20480Mb total
Creating files for the test...
[root@ns30093xx ~]# sysbench --test=fileio --file-total-size=20G --file-test-mode=rndrw --max-time=300 --max-requests=0 run
sysbench 0.4.12:  multi-threaded system evaluation benchmark

Running the test with following options:
Number of threads: 1

Extra file open flags: 0
128 files, 160Mb each
20Gb total file size
Block size 16Kb
Number of random requests for random IO: 0
Read/Write ratio for combined random IO test: 1.50
Periodic FSYNC enabled, calling fsync() each 100 requests.
Calling fsync() at the end of test, Enabled.
Using synchronous I/O mode
Doing random r/w test
Threads started!
Time limit exceeded, exiting...
Done.

Operations performed:  1926300 Read, 1284200 Write, 4109338 Other = 7319838 Total
Read 29.393Gb  Written 19.595Gb  Total transferred 48.988Gb  (167.21Mb/sec)
10701.66 Requests/sec executed

Test execution summary:
    total time:                          300.0001s
    total number of events:              3210500
    total time taken by event execution: 186.3406
    per-request statistics:
         min:                                  0.00ms
         avg:                                  0.06ms
         max:                                  3.88ms
         approx.  95 percentile:               0.20ms

Threads fairness:
    events (avg/stddev):           3210500.0000/0.00
    execution time (avg/stddev):   186.3406/0.00

Serverbear

Тесты Serverbear

Судя по которым этот сервер является довольно выгодным по сравнению с конкурентами.

Выводы

Это отличный сервер за свои деньги. Обычно с этими серверами практически не возникает проблем. Также в пользу этих серверов говорит и их популярность. Все мои знакомые с игровыми серверами уже давно переехали в OVH =)