Привет!
Публикую сразу два теста подряд. В этом посте тест VPS SSD Ferrum, а во втором VPS KVM Ferrum. Отличие только в том что здесь у нас SSD, а там HDD. Разница в деньгах 50 рублей (250 руб./месяц VPS SSD Ferrum и 200 руб./месяц второй).
Вообще считаю ihor лучшим выбором для аренды виртуального сервера в РФ. Цены здесь на уровне конкурентов, но есть одно неоспоримое преимущество - панель ISPmanager 5 Lite в подарок. Также и сам сервис работает довольно хорошо.
Итак, краткий тест:
IP-адрес почему то определяется как Волгоград, хотя на самом деле это Москва.
[rail@localhost ~]$ ping 185.87.48.xx PING 185.87.48.xx (185.87.48.xx) 56(84) bytes of data. 64 bytes from 185.87.48.xx: icmp_seq=1 ttl=56 time=18.0 ms 64 bytes from 185.87.48.xx: icmp_seq=2 ttl=56 time=18.1 ms 64 bytes from 185.87.48.xx: icmp_seq=3 ttl=56 time=17.4 ms 64 bytes from 185.87.48.xx: icmp_seq=4 ttl=56 time=17.6 ms 64 bytes from 185.87.48.xx: icmp_seq=5 ttl=56 time=19.9 ms 64 bytes from 185.87.48.xx: icmp_seq=6 ttl=56 time=17.9 ms 64 bytes from 185.87.48.xx: icmp_seq=7 ttl=56 time=17.8 ms 64 bytes from 185.87.48.xx: icmp_seq=8 ttl=56 time=18.0 ms 64 bytes from 185.87.48.xx: icmp_seq=9 ttl=56 time=17.9 ms 64 bytes from 185.87.48.xx: icmp_seq=10 ttl=56 time=17.5 ms ^C --- 185.87.48.xx ping statistics --- 10 packets transmitted, 10 received, 0% packet loss, time 9003ms rtt min/avg/max/mdev = 17.455/18.064/19.950/0.674 ms
Да, Москва, что подтверждают пинги в 17мс из Ульяновска =)
Очень шустрый SSD:
[root@ihortst ~]# dd if=/dev/zero of=test bs=64k count=16k conv=fdatasync 16384+0 записей получено 16384+0 записей отправлено скопировано 1073741824 байта (1,1 GB), 3,72796 c, 288 MB/c [root@ihortst ~]# rm -f test [root@ihortst ~]# dd if=/dev/zero of=test bs=64k count=16k conv=fdatasync 16384+0 записей получено 16384+0 записей отправлено скопировано 1073741824 байта (1,1 GB), 3,47502 c, 309 MB/c [root@ihortst ~]# rm -f test [root@ihortst ~]# dd if=/dev/zero of=test bs=64k count=16k conv=fdatasync 16384+0 записей получено 16384+0 записей отправлено скопировано 1073741824 байта (1,1 GB), 3,5461 c, 303 MB/c
Вот такой вывод по железу:
[root@ihortst ~]# inxi -b
System: Host: ihortst.rhdev.ru Kernel: 3.10.0-327.4.4.el7.x86_64 x86_64 (64 bit) Console: tty 0
Distro: CentOS Linux release 7.2.1511 (Core)
Machine: System: Red Hat product: KVM v: RHEL 7.0.0 PC (i440FX + PIIX 1996)
Mobo: N/A model: N/A Bios: Sea v: 0.5.1 date: 01/01/2011
CPU: Single core Intel Xeon E5620 (-MCP-) speed: 2400 MHz (max)
Graphics: Card: Cirrus Logic GD 5446
Display Server: N/A driver: N/A tty size: 182x27 Advanced Data: N/A for root out of X
Network: Card: Red Hat Virtio network device driver: virtio-pci
Drives: HDD Total Size: 21.5GB (5.0% used)
Info: Processes: 67 Uptime: 5 min Memory: 96.5/993.1MB Init: systemd runlevel: 3
Client: Shell (bash) inxi: 2.2.31
Диск в 20 гигабайт:
[root@ihortst ~]# df -H Файловая система Размер Использовано Дост Использовано% Cмонтировано в /dev/vda1 22G 1,1G 20G 6% / devtmpfs 512M 0 512M 0% /dev tmpfs 521M 0 521M 0% /dev/shm tmpfs 521M 6,8M 514M 2% /run tmpfs 521M 0 521M 0% /sys/fs/cgroup none 521M 0 521M 0% /tmp tmpfs 105M 0 105M 0% /run/user/0
Проц
[root@ihortst ~]# cat /proc/cpuinfo processor : 0 vendor_id : GenuineIntel cpu family : 6 model : 44 model name : Intel(R) Xeon(R) CPU E5620 @ 2.40GHz stepping : 2 microcode : 0x1 cpu MHz : 2400.084 cache size : 4096 KB physical id : 0 siblings : 1 core id : 0 cpu cores : 1 apicid : 0 initial apicid : 0 fpu : yes fpu_exception : yes cpuid level : 11 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ss syscall nx pdpe1gb rdtscp lm constant_tsc arch_perfmon rep_good nopl pni pclmulqdq ssse3 cx16 pcid sse4_1 sse4_2 x2apic popcnt aes hypervisor lahf_lm tsc_adjust bogomips : 4800.16 clflush size : 64 cache_alignment : 64 address sizes : 40 bits physical, 48 bits virtual power management:
ОЗУ
[root@ihortst ~]# cat /proc/meminfo MemTotal: 1016916 kB MemFree: 648900 kB MemAvailable: 817140 kB Buffers: 17840 kB Cached: 255144 kB SwapCached: 0 kB Active: 154488 kB Inactive: 156724 kB Active(anon): 38384 kB Inactive(anon): 6444 kB Active(file): 116104 kB Inactive(file): 150280 kB Unevictable: 0 kB Mlocked: 0 kB SwapTotal: 0 kB SwapFree: 0 kB Dirty: 12584 kB Writeback: 0 kB AnonPages: 38256 kB Mapped: 15468 kB Shmem: 6604 kB Slab: 37776 kB SReclaimable: 28960 kB SUnreclaim: 8816 kB KernelStack: 1168 kB PageTables: 2568 kB NFS_Unstable: 0 kB Bounce: 0 kB WritebackTmp: 0 kB CommitLimit: 508456 kB Committed_AS: 135472 kB VmallocTotal: 34359738367 kB VmallocUsed: 6692 kB VmallocChunk: 34359728891 kB HardwareCorrupted: 0 kB AnonHugePages: 0 kB HugePages_Total: 0 HugePages_Free: 0 HugePages_Rsvd: 0 HugePages_Surp: 0 Hugepagesize: 2048 kB DirectMap4k: 53240 kB DirectMap2M: 995328 kB DirectMap1G: 0 kB
Sysbench CPU
[root@ihortst ~]# 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: 28.6383s
total number of events: 10000
total time taken by event execution: 28.6361
per-request statistics:
min: 2.74ms
avg: 2.86ms
max: 4.77ms
approx. 95 percentile: 3.07ms
Threads fairness:
events (avg/stddev): 10000.0000/0.00
execution time (avg/stddev): 28.6361/0.00
[root@ihortst ~]# 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.1644s
total number of events: 64
total time taken by event execution: 0.1609
per-request statistics:
min: 2.44ms
avg: 2.51ms
max: 2.88ms
approx. 95 percentile: 2.71ms
Threads fairness:
events (avg/stddev): 1.0000/0.00
execution time (avg/stddev): 0.0025/0.00
Sysbench memory
[root@ihortst ~]# sysbench --test=memory --num-threads=4 --memory-total-size=1G 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: 1024M
Memory operations type: write
Memory scope type: global
Threads started!
Done.
Operations performed: 1048576 (1480305.90 ops/sec)
1024.00 MB transferred (1445.61 MB/sec)
Test execution summary:
total time: 0.7084s
total number of events: 1048576
total time taken by event execution: 2.1918
per-request statistics:
min: 0.00ms
avg: 0.00ms
max: 66.01ms
approx. 95 percentile: 0.00ms
Threads fairness:
events (avg/stddev): 262144.0000/2244.20
execution time (avg/stddev): 0.5479/0.00
С CPU и ОЗУ все норм.
Sysbench disk io
[root@ihortst ~]# sysbench --test=fileio --file-total-size=2G prepare
sysbench 0.4.12: multi-threaded system evaluation benchmark
128 files, 16384Kb each, 2048Mb total
Creating files for the test...
[root@ihortst ~]# sysbench --test=fileio --file-total-size=2G --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, 16Mb each
2Gb 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: 23940 Read, 15960 Write, 50982 Other = 90882 Total
Read 374.06Mb Written 249.38Mb Total transferred 623.44Mb (2.0781Mb/sec)
133.00 Requests/sec executed
Test execution summary:
total time: 300.0069s
total number of events: 39900
total time taken by event execution: 22.6772
per-request statistics:
min: 0.00ms
avg: 0.57ms
max: 134.21ms
approx. 95 percentile: 3.02ms
Threads fairness:
events (avg/stddev): 39900.0000/0.00
execution time (avg/stddev): 22.6772/0.00
А вот этот тест провалился, что-то пошло не так.
Serverbear
Тесты Serverbear
Выводы
Очень хорошее предложение по соотношению цена/качество. Рекомендую.