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.
How much power does a Runabove core have?
This question of how much power there is in a core has come up again. I find it all confusing. I guess it isn't just a Runabove question.
Does 1 core mean that if there are cores available, the maximum you can use is just 1?
Is the core dedicated to you or is it shared?
How many threads are available to the core?
What CPUs are used by Runabove and how many cores and threads to they have?

Comments
Best would be to benchmark it with serverbear and compare.
My Windows 2012 VM says this in Task Manager:
Intel Xeon E312xx (Sandy Bridge)
3.70GHz
I saw a post on the community forum indicating you're free to use 100% of the CPU.
A simple benchmark I ran on the CPU
(time echo "scale=5000; 4*a(1)" | bc -lq) 2>&1 real 0m37.871s user 0m37.794s sys 0m0.020s openssl speed rsa Doing 512 bit private rsa's for 10s: 98029 512 bit private RSA's in 10.00s Doing 512 bit public rsa's for 10s: 1038424 512 bit public RSA's in 10.00s Doing 1024 bit private rsa's for 10s: 24608 1024 bit private RSA's in 9.96s Doing 1024 bit public rsa's for 10s: 409402 1024 bit public RSA's in 9.96s Doing 2048 bit private rsa's for 10s: 4086 2048 bit private RSA's in 9.97s Doing 2048 bit public rsa's for 10s: 129432 2048 bit public RSA's in 9.98s Doing 4096 bit private rsa's for 10s: 537 4096 bit private RSA's in 9.99s Doing 4096 bit public rsa's for 10s: 35462 4096 bit public RSA's in 10.00s OpenSSL 1.0.1e 11 Feb 2013 built on: Thu Jan 8 21:12:53 UTC 2015 options:bn(64,64) rc4(16x,int) des(idx,cisc,16,int) aes(partial) blowfish(idx) compiler: gcc -fPIC -DOPENSSL_PIC -DZLIB -DOPENSSL_THREADS -D_REENTRANT -DDSO_DLFCN -DHAVE_DLFCN_H -m64 -DL_ENDIAN -DTERMIO -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -D_FORTIFY_SOURCE=2 -Wl,-z,relro -Wa,--noexecstack -Wall -DMD32_REG_T=int -DOPENSSL_IA32_SSE2 -DOPENSSL_BN_ASM_MONT -DOPENSSL_BN_ASM_MONT5 -DOPENSSL_BN_ASM_GF2m -DSHA1_ASM -DSHA256_ASM -DSHA512_ASM -DMD5_ASM -DAES_ASM -DVPAES_ASM -DBSAES_ASM -DWHIRLPOOL_ASM -DGHASH_ASM sign verify sign/s verify/s rsa 512 bits 0.000102s 0.000010s 9802.9 103842.4 rsa 1024 bits 0.000405s 0.000024s 2470.7 41104.6 rsa 2048 bits 0.002440s 0.000077s 409.8 12969.1 rsa 4096 bits 0.018603s 0.000282s 53.8 3546.2I did a UnixBench on the smallest sandbox instance back in november 2014, looked like this:
Benchmark Run: Sa Nov 15 2014 13:08:26 - 13:37:08 1 CPU in system; running 1 parallel copy of tests System Benchmarks Index Values BASELINE RESULT INDEX Dhrystone 2 using register variables 116700.0 40234485.8 3447.7 Double-Precision Whetstone 55.0 3557.6 646.8 Execl Throughput 43.0 6694.6 1556.9 File Copy 1024 bufsize 2000 maxblocks 3960.0 1233557.7 3115.0 File Copy 256 bufsize 500 maxblocks 1655.0 434201.9 2623.6 File Copy 4096 bufsize 8000 maxblocks 5800.0 3106308.1 5355.7 Pipe Throughput 12440.0 2800174.0 2250.9 Pipe-based Context Switching 4000.0 502641.6 1256.6 Process Creation 126.0 21921.7 1739.8 Shell Scripts (1 concurrent) 42.4 8109.2 1912.6 Shell Scripts (8 concurrent) 6.0 1089.2 1815.4 System Call Overhead 15000.0 5749044.6 3832.7 ======== System Benchmarks Index Score 2153.6Steadfast are dedicated to you. One VM per box means the whole box is dedicated to you. Power8 appears to be dedicated as well, the smaller option giving you one core (eight threads), while the larger option gives you the whole box.
The only question is Sandbox resources, where it hasn't been made clear one way or the other if the core is dedicated. (Though I suspect it is.)