New on LowEndTalk? Please Register and read our Community Rules.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
Prometeus VZ7 1GB 25GB SSD 2.93TB OpenVZ Benchmark
ErawanArifNugroho
Member
I've got this offer from @Prometeus with the 50% discount, another same promo is also in WHT, so maybe this one can be used as benchmark reference.
Disk Space: 25GB SSD CPU Cores: 4 RAM: 1024 MB vSwap: 512MB Bandwidth: 2.93TB 1 IPv4 & 4 IPv6 OpenVZ
CPU Info
# cat /proc/cpuinfo processor : 0 vendor_id : GenuineIntel cpu family : 6 model : 45 model name : Intel(R) Xeon(R) CPU E5-2620 0 @ 2.00GHz stepping : 7 cpu MHz : 1999.840 cache size : 15360 KB physical id : 0 siblings : 12 core id : 0 cpu cores : 6 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 xtopology nonstop_tsc aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr pdcm dca sse4_1 sse4_2 x2apic popcnt aes xsave avx lahf_lm ida arat epb xsaveopt pln pts dts tpr_shadow vnmi flexpriority ept vpid bogomips : 3999.68 clflush size : 64 cache_alignment : 64 address sizes : 46 bits physical, 48 bits virtual power management: processor : 1 vendor_id : GenuineIntel cpu family : 6 model : 45 model name : Intel(R) Xeon(R) CPU E5-2620 0 @ 2.00GHz stepping : 7 cpu MHz : 1999.840 cache size : 15360 KB physical id : 0 siblings : 12 core id : 1 cpu cores : 6 apicid : 2 initial apicid : 2 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 xtopology nonstop_tsc aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr pdcm dca sse4_1 sse4_2 x2apic popcnt aes xsave avx lahf_lm ida arat epb xsaveopt pln pts dts tpr_shadow vnmi flexpriority ept vpid bogomips : 3999.68 clflush size : 64 cache_alignment : 64 address sizes : 46 bits physical, 48 bits virtual power management: processor : 2 vendor_id : GenuineIntel cpu family : 6 model : 45 model name : Intel(R) Xeon(R) CPU E5-2620 0 @ 2.00GHz stepping : 7 cpu MHz : 1999.840 cache size : 15360 KB physical id : 0 siblings : 12 core id : 2 cpu cores : 6 apicid : 4 initial apicid : 4 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 xtopology nonstop_tsc aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr pdcm dca sse4_1 sse4_2 x2apic popcnt aes xsave avx lahf_lm ida arat epb xsaveopt pln pts dts tpr_shadow vnmi flexpriority ept vpid bogomips : 3999.68 clflush size : 64 cache_alignment : 64 address sizes : 46 bits physical, 48 bits virtual power management: processor : 3 vendor_id : GenuineIntel cpu family : 6 model : 45 model name : Intel(R) Xeon(R) CPU E5-2620 0 @ 2.00GHz stepping : 7 cpu MHz : 1999.840 cache size : 15360 KB physical id : 0 siblings : 12 core id : 3 cpu cores : 6 apicid : 6 initial apicid : 6 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 xtopology nonstop_tsc aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr pdcm dca sse4_1 sse4_2 x2apic popcnt aes xsave avx lahf_lm ida arat epb xsaveopt pln pts dts tpr_shadow vnmi flexpriority ept vpid bogomips : 3999.68 clflush size : 64 cache_alignment : 64 address sizes : 46 bits physical, 48 bits virtual power management:
Memory Info
# cat /proc/meminfo MemTotal: 1048576 kB MemFree: 901008 kB Cached: 134820 kB Active: 91064 kB Inactive: 48164 kB Active(anon): 4400 kB Inactive(anon): 8 kB Active(file): 86664 kB Inactive(file): 48156 kB Unevictable: 0 kB Mlocked: 0 kB SwapTotal: 524288 kB SwapFree: 524288 kB Dirty: 0 kB Writeback: 0 kB AnonPages: 4408 kB Shmem: 5120 kB Slab: 8296 kB SReclaimable: 6500 kB SUnreclaim: 1796 kB
Freevps.sh
# wget freevps.us/downloads/bench.sh -O - -o /dev/null|bash CPU model : Intel(R) Xeon(R) CPU E5-2620 0 @ 2.00GHz Number of cores : 4 CPU frequency : 1999.840 MHz Total amount of ram : 1024 MB Total amount of swap : 512 MB System uptime : 6 min, Download speed from CacheFly: 5.95MB/s Download speed from Linode, Atlanta GA: 280KB/s Download speed from Linode, Dallas, TX: 4.06MB/s Download speed from Linode, Tokyo, JP: 3.90MB/s Download speed from Linode, London, UK: Download speed from Leaseweb, Haarlem, NL: 2.41MB/s Download speed from Softlayer, Singapore: 3.79MB/s Download speed from Softlayer, Seattle, WA: 6.05MB/s Download speed from Softlayer, San Jose, CA: 258KB/s Download speed from Softlayer, Washington, DC: 9.61MB/s I/O speed : 500 MB/s
Comments
Inodes
Disk Space
Download Test
Ping and Traceroute
IO Test
IOPING
UnixBench
# # # # # # # ##### ###### # # #### # # # # ## # # # # # # # ## # # # # # # # # # # # ## ##### ##### # # # # ###### # # # # # # ## # # # # # # # # # # # # ## # # # # # # # ## # # # # #### # # # # # ##### ###### # # #### # # Version 5.1.3 Based on the Byte Magazine Unix Benchmark Multi-CPU version Version 5 revisions by Ian Smith, Sunnyvale, CA, USA January 13, 2011 johantheghost at yahoo period com 1 x Dhrystone 2 using register variables 1 2 3 4 5 6 7 8 9 10 1 x Double-Precision Whetstone 1 2 3 4 5 6 7 8 9 10 1 x Execl Throughput 1 2 3 1 x File Copy 1024 bufsize 2000 maxblocks 1 2 3 1 x File Copy 256 bufsize 500 maxblocks 1 2 3 1 x File Copy 4096 bufsize 8000 maxblocks 1 2 3 1 x Pipe Throughput 1 2 3 4 5 6 7 8 9 10 1 x Pipe-based Context Switching 1 2 3 4 5 6 7 8 9 10 1 x Process Creation 1 2 3 1 x System Call Overhead 1 2 3 4 5 6 7 8 9 10 1 x Shell Scripts (1 concurrent) 1 2 3 1 x Shell Scripts (8 concurrent) 1 2 3 4 x Dhrystone 2 using register variables 1 2 3 4 5 6 7 8 9 10 4 x Double-Precision Whetstone 1 2 3 4 5 6 7 8 9 10 4 x Execl Throughput 1 2 3 4 x File Copy 1024 bufsize 2000 maxblocks 1 2 3 4 x File Copy 256 bufsize 500 maxblocks 1 2 3 4 x File Copy 4096 bufsize 8000 maxblocks 1 2 3 4 x Pipe Throughput 1 2 3 4 5 6 7 8 9 10 4 x Pipe-based Context Switching 1 2 3 4 5 6 7 8 9 10 4 x Process Creation 1 2 3 4 x System Call Overhead 1 2 3 4 5 6 7 8 9 10 4 x Shell Scripts (1 concurrent) 1 2 3 4 x Shell Scripts (8 concurrent) 1 2 3 ======================================================================== BYTE UNIX Benchmarks (Version 5.1.3) System: it: GNU/Linux OS: GNU/Linux -- 2.6.32-042stab063.2 -- #1 SMP Tue Oct 23 16:24:09 MSK 2012 Machine: i686 (unknown) Language: en_US.utf8 (charmap="ANSI_X3.4-1968", collate="ANSI_X3.4-1968") CPU 0: Intel(R) Xeon(R) CPU E5-2620 0 @ 2.00GHz (3999.7 bogomips) Hyper-Threading, x86-64, MMX, Physical Address Ext, SYSENTER/SYSEXIT, SYSCALL/SYSRET, Intel virtualization CPU 1: Intel(R) Xeon(R) CPU E5-2620 0 @ 2.00GHz (3999.7 bogomips) Hyper-Threading, x86-64, MMX, Physical Address Ext, SYSENTER/SYSEXIT, SYSCALL/SYSRET, Intel virtualization CPU 2: Intel(R) Xeon(R) CPU E5-2620 0 @ 2.00GHz (3999.7 bogomips) Hyper-Threading, x86-64, MMX, Physical Address Ext, SYSENTER/SYSEXIT, SYSCALL/SYSRET, Intel virtualization CPU 3: Intel(R) Xeon(R) CPU E5-2620 0 @ 2.00GHz (3999.7 bogomips) Hyper-Threading, x86-64, MMX, Physical Address Ext, SYSENTER/SYSEXIT, SYSCALL/SYSRET, Intel virtualization 02:47:12 up 6:55, 0 users, load average: 0.00, 0.00, 0.00; runlevel 2 ------------------------------------------------------------------------ Benchmark Run: Fri Nov 16 2012 02:47:12 - 03:15:09 4 CPUs in system; running 1 parallel copy of tests Dhrystone 2 using register variables 8009812.8 lps (10.0 s, 7 samples) Double-Precision Whetstone 1189.2 MWIPS (10.2 s, 7 samples) Execl Throughput 1730.0 lps (30.0 s, 2 samples) File Copy 1024 bufsize 2000 maxblocks 245946.9 KBps (30.0 s, 2 samples) File Copy 256 bufsize 500 maxblocks 67626.9 KBps (30.0 s, 2 samples) File Copy 4096 bufsize 8000 maxblocks 740951.4 KBps (30.0 s, 2 samples) Pipe Throughput 404003.1 lps (10.0 s, 7 samples) Pipe-based Context Switching 65748.8 lps (10.0 s, 7 samples) Process Creation 5250.3 lps (30.0 s, 2 samples) Shell Scripts (1 concurrent) 3552.9 lpm (60.0 s, 2 samples) Shell Scripts (8 concurrent) 1146.5 lpm (60.0 s, 2 samples) System Call Overhead 305373.3 lps (10.0 s, 7 samples) System Benchmarks Index Values BASELINE RESULT INDEX Dhrystone 2 using register variables 116700.0 8009812.8 686.4 Double-Precision Whetstone 55.0 1189.2 216.2 Execl Throughput 43.0 1730.0 402.3 File Copy 1024 bufsize 2000 maxblocks 3960.0 245946.9 621.1 File Copy 256 bufsize 500 maxblocks 1655.0 67626.9 408.6 File Copy 4096 bufsize 8000 maxblocks 5800.0 740951.4 1277.5 Pipe Throughput 12440.0 404003.1 324.8 Pipe-based Context Switching 4000.0 65748.8 164.4 Process Creation 126.0 5250.3 416.7 Shell Scripts (1 concurrent) 42.4 3552.9 837.9 Shell Scripts (8 concurrent) 6.0 1146.5 1910.8 System Call Overhead 15000.0 305373.3 203.6 ======== System Benchmarks Index Score 477.5 ------------------------------------------------------------------------ Benchmark Run: Fri Nov 16 2012 03:15:10 - 03:43:26 4 CPUs in system; running 4 parallel copies of tests Dhrystone 2 using register variables 35491744.8 lps (10.0 s, 7 samples) Double-Precision Whetstone 6294.0 MWIPS (11.5 s, 7 samples) Execl Throughput 9381.2 lps (30.0 s, 2 samples) File Copy 1024 bufsize 2000 maxblocks 506946.9 KBps (30.0 s, 2 samples) File Copy 256 bufsize 500 maxblocks 125569.5 KBps (30.0 s, 2 samples) File Copy 4096 bufsize 8000 maxblocks 1528917.7 KBps (30.0 s, 2 samples) Pipe Throughput 2040376.9 lps (10.0 s, 7 samples) Pipe-based Context Switching 446550.9 lps (10.0 s, 7 samples) Process Creation 20168.7 lps (30.0 s, 2 samples) Shell Scripts (1 concurrent) 11513.1 lpm (60.0 s, 2 samples) Shell Scripts (8 concurrent) 1397.2 lpm (60.1 s, 2 samples) System Call Overhead 1440787.8 lps (10.0 s, 7 samples) System Benchmarks Index Values BASELINE RESULT INDEX Dhrystone 2 using register variables 116700.0 35491744.8 3041.3 Double-Precision Whetstone 55.0 6294.0 1144.4 Execl Throughput 43.0 9381.2 2181.7 File Copy 1024 bufsize 2000 maxblocks 3960.0 506946.9 1280.2 File Copy 256 bufsize 500 maxblocks 1655.0 125569.5 758.7 File Copy 4096 bufsize 8000 maxblocks 5800.0 1528917.7 2636.1 Pipe Throughput 12440.0 2040376.9 1640.2 Pipe-based Context Switching 4000.0 446550.9 1116.4 Process Creation 126.0 20168.7 1600.7 Shell Scripts (1 concurrent) 42.4 11513.1 2715.4 Shell Scripts (8 concurrent) 6.0 1397.2 2328.6 System Call Overhead 15000.0 1440787.8 960.5 ======== System Benchmarks Index Score 1627.8Serverbear
http://serverbear.com/benchmark/2012/11/16/2EWbzDqtTX1Qq7gb
Thanks for the benchmark - some tasty IO there. One thing I've noticed is a lot of benchmark posting without analysis (typically only comments when something is very bad). Would be good to see people providing their analysis of the benchmarks in addition to the numbers. What do you look for/expect (at that price-point) vs. benchmark result.
craigb : I'm not looking / comparing from price vs results.
, so people would not try to run the same benchmark process over and over that will kill the server
Just providing if someone needed the benchmark results.
In our case, you can run the benchmark, the servers will not die, only dont run them on cron on 24 cores nodes,that will not be nice and will earn a cancellation :P
@Maounique, I don't even know how to run cron ( except having the tutorial from installing a software, like vnstat ) and scripting in linux, so no need to worry
Looks good from disk and IO. I don't bother much with the CPU analysis, since regulation and throttle of the CPU is unknown to end user.
One thing that stuck out was the network. Isn't this supposed to be a gigabit connection?
Download speed from CacheFly: 5.95MB/s (not good)
Download speed from Linode, Atlanta GA: 280KB/s (horrible)
Download speed from Linode, Dallas, TX: 4.06MB/s (mediocre for busy 100Mbps)
Download speed from Linode, Tokyo, JP: 3.90MB/s (mediocre for busy 100Mbps)
Download speed from Leaseweb, Haarlem, NL: 2.41MB/s (this is aweful -- should be very fast since same continent)
Download speed from Softlayer, Singapore: 3.79MB/s (acceptable since so far)
Download speed from Softlayer, Seattle, WA: 6.05MB/s (alright for 100Mbps)
Download speed from Softlayer, San Jose, CA: 258KB/s (might want to use carrier pigeons instead)
Download speed from Softlayer, Washington, DC: 9.61MB/s (good for 100Mbps offer)
Network seems fubar'ed.
That script continues to irritate me since so dependent on the same few networks.
Curious how the network performs with other well known speed test points.... To determine if it is peering that is the problem or over saturation.
PS: I am curious since I've been considering this provider and like what I've seen and heard prior to these numbers.
Well, this is curious for me too, the port is 1 gbit AND the node is far from full.
I will test on my VPS see what gives (granted, another node, but should not matter much, if anything should be worse).
EDIT:
Seems a decent all-rounder, well, except SJ and London. We have ppl that push/pull 10 TB on one VPS in a month, they couldnt if the network was bad.
North Italy is linked to germany L3, that test has no DE location, tho.
But it is strange since my node is much more loaded than the SSD one, and now is peak time in EU DCs too.
Erawan should have had better results. Maybe redo the test later ?
Better numbers there @Maounique. Thanks for the honesty on the matter since materially interested
I don't expect a EURO provider to be performing highly to Asia. To Cachefly, yes. To Haarlem, NL, yes.
Better check OVH, Hetzner and other big network speed tests to determine what is going on there (node heavy data use, upstream issues, etc.).
I will try to do the test again, because my current connection is little laggy now
I've been having routing issues today from my Prometeus nodes to the US. So today may not be the best day to test connectivity.