Little bit confusing in the admin interface. It seems like these new processors replace the old C1 offer. This is the cpuinfo of the new one:

cat /proc/cpuinfo
processor : 0
BogoMIPS : 200.00
Features : fp asimd evtstrm aes pmull sha1 sha2 crc32 atomics
CPU implementer : 0x43
CPU architecture: 8
CPU variant : 0x1
CPU part : 0x0a1
CPU revision : 1

processor : 1
BogoMIPS : 200.00
Features : fp asimd evtstrm aes pmull sha1 sha2 crc32 atomics
CPU implementer : 0x43
CPU architecture: 8
CPU variant : 0x1
CPU part : 0x0a1

For comparison, this was the old C1, their prior ARM offering they mention in the blog post:

Processor : Marvell PJ4Bv7 Processor rev 2 (v7l)
processor : 0
BogoMIPS : 1332.01

processor : 1
BogoMIPS : 1332.01

processor : 2
BogoMIPS : 1332.01

processor : 3
BogoMIPS : 1332.01

Features : swp half thumb fastmult vfp edsp vfpv3 tls
CPU implementer : 0x56
CPU architecture: 7
CPU variant : 0x2
CPU part : 0x584
CPU revision : 2
Hardware : Online Labs C1
Revision : 0000
Serial : 0000000000000000

I take it the BogoMips are just a false info in the kernel interface.

For performance, I ran `sysbench --test=cpu --cpu-max-prime=1000 run` on both (first I tried that with max-prime=20000, but that did not finish in a reasonable time span on the old server).

New:

Number of threads: 1

Doing CPU performance benchmark

Threads started!
Done.

Maximum prime number checked in CPU test: 1000

Test execution summary:
total time: 0.6541s
total number of events: 10000
total time taken by event execution: 0.6507
per-request statistics:
min: 0.06ms
avg: 0.07ms
max: 0.14ms
approx. 95 percentile: 0.06ms

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

Old:

Number of threads: 1

Doing CPU performance benchmark

Threads started!
Done.

Maximum prime number checked in CPU test: 1000

Test execution summary:
total time: 10.1997s
total number of events: 10000
total time taken by event execution: 10.1909
per-request statistics:
min: 1.02ms
avg: 1.02ms
max: 1.22ms
approx. 95 percentile: 1.02ms

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

When using the additional cores (2 for the new, 4 for the old):

New:

Number of threads: 2

Doing CPU performance benchmark

Threads started!
Done.

Maximum prime number checked in CPU test: 1000

Test execution summary:
total time: 0.3282s
total number of events: 10000
total time taken by event execution: 0.6523
per-request statistics:
min: 0.06ms
avg: 0.07ms
max: 0.28ms
approx. 95 percentile: 0.06ms

Threads fairness:
events (avg/stddev): 5000.0000/2.00
execution time (avg/stddev): 0.3261/0.00

Old:

Number of threads: 4

Doing CPU performance benchmark

Threads started!
Done.

Maximum prime number checked in CPU test: 1000

Test execution summary:
total time: 2.5527s
total number of events: 10000
total time taken by event execution: 10.1983
per-request statistics:
min: 1.02ms
avg: 1.02ms
max: 5.49ms
approx. 95 percentile: 1.02ms

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

The new processors seem to be a lot more powerful. I run my blog on that old C1 (that might have skewed results somewhat if they were close, but they are not). I think I'll move it over asap.

Edit:

I have another Scaleway instance that runs https://www.pc-kombo.de, and is a C2S instance, which is the also mentioned X64 offering of theirs. It is more expensive, as it has more cores, but if matching those the ARMv8 seems to actually be faster. That's the performance of the C2S:

Number of threads: 1

Doing CPU performance benchmark

Threads started!
Done.

Maximum prime number checked in CPU test: 1000

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

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

With 2 threads:

Number of threads: 2

Doing CPU performance benchmark

Threads started!
Done.

Maximum prime number checked in CPU test: 1000

Test execution summary:
total time: 0.4489s
total number of events: 10000
total time taken by event execution: 0.8752
per-request statistics:
min: 0.08ms
avg: 0.09ms
max: 20.09ms
approx. 95 percentile: 0.08ms

Threads fairness:
events (avg/stddev): 5000.0000/23.00
execution time (avg/stddev): 0.4376/0.01

Seems like I should move that as well.