LEBRE-X: Nexus Bytes Ryzen NVMe VPS

The very first LEBRE-X review goes to our Nexus Bytes Ryzen NVMe reference box REBOX1. Readers will already be familiar with REBOX1 because it is the reference box for value comparison using the LEBRE methodology. However, although the LEBRE methodology provides a clear measure of value based on paper specifications, it cannot adequately reflect actual performance. Therefore, we’ve subjected REBOX1 to an extended period of benchmarking as outlined in the LEBRE-X methodology.

The detailed specifications of the VPS is as follows:

  • Processor: Ryzen 7 3700X 8-Core Processor
  • 2 vCPUs @ 3593.248 MHz
  • 2GB RAM
  • 30GB NVMe Disk
  • 1Gpbs Port
  • AES-NI: Enabled
  • VM-x/AMD-V: Enabled
  • Location: Germany

With AES-NI enabled, there is no performance penalty on LUKS encryption using AES on the VPS. Also, with VM-x/AMD-V enabled, nested virtualization is possible, allowing deploying of solutions such as Proxmox. Certainly a nice CPU feature set.

We now turn to the results of our extended benchmarking, which we ran daily for 33 days from 14 December 2019 to 15 January 2020. All charts are interactive (i.e. you can mouse over the lines to examine each data point).

Geekbench 5 Test

Geekbench 5 offers a quick overview of CPU and RAM performance in a single score. The following chart shows the single and multi-core scores of the Nexus Bytes Ryzen NVMe VPS across our test period.

powered by Advanced iFrame. Get the Pro version on CodeCanyon.

Despite the fair-share policy of Nexus Bytes, it can be seen that the VPS is both very high performing and the performance is very consistent for both single (mean score 1143, SD 16.1) and multi-core (mean score 2122, SD 61.2) over the period of testing. This indicates that the host node is very likely not oversold and well-monitored, ensuring consistently high performance for your applications whenever you require.

fio Random Read-Write

We use fio to benchmark disk performance because random read-write is more indicative of real-world use compared to sequential read-write, which normally generates impressive metrics but is a poor indicator of real-world performance. The following charts show the random read and write IOPS performance at 4k, 64k and 256k block sizes.

powered by Advanced iFrame. Get the Pro version on CodeCanyon.

powered by Advanced iFrame. Get the Pro version on CodeCanyon.

The NVMe disk clearly show its superior performance in terms of IOPS. The Nexus Bytes VPS is extremely fast and stable in performance when it comes to random reading (mean IOPS 80811, SD 4951) and writing (mean IOPS 80899, SD 4956) at 4k block sizes.

Speed is still excellent for random reading (mean IOPS 30185, SD 7897) and writing (mean IOPS 30319, SD 7926) at 64k block sizes, although the variability of performance increases as evident from the higher standard deviation.

For our most gruelling 256k block size random read-write test, the speed in terms of reading (mean IOPS 9386, SD 2402) and writing (mean IOPS 9241, SD 2366) was still stellar, with some variability similar to the 64k block size test.

The overall conclusion from the fio results is crystal-clear: there is very likely no problem running applications that require strong IOPS performance. Assuming that the database is well-tuned, this Nexus Bytes VPS is likely to be able to deliver a consistently buttery-smooth experience, even for busy database driven CMS websites.

ioping Latency

We use ioping to measure how responsive the disk is to requests. The chart below shows the results of average response times to 30 requests.

powered by Advanced iFrame. Get the Pro version on CodeCanyon.

The spikes in the chart may worry some of you, but there is actually no cause for alarm. The disk response times are measured in microseconds (mean 373.5, SD 126.6). A microsecond (μs) is one millionth of a second, so despite the spikes, you will not notice any real-world difference. Also, if the ioping results are too flat, it is indicative of very low disk activity (meaning the host node is very empty) or there is some caching mechanism going on.

iperf3 Speeds

We use iperf3 to measure outbound internet speeds (i.e. how fast the VPS sends data out to users) to our own collection of iperf3 servers. Keep in mind that there are many factors involved in transmitting data across networks, especially across vast geographical distances. Spikes are not unusual. Note that we present our data in megabytes per second.

We first present the chart for European locations.

powered by Advanced iFrame. Get the Pro version on CodeCanyon.

We see generally consistent performance to our Polish server (mean 107.9, SD 6.7). The spikes to our Romanian server (mean 67.1, SD 14.3) is more of an issue with the network of our Romanian server. Generally, we see speedy network speeds in Europe.

We now present the chart for our North America servers.

powered by Advanced iFrame. Get the Pro version on CodeCanyon.

You must be wondering about that huge dip in network speed to Utah (mean 95.0, SD 32.6) during the Christmas holiday period. We are not sure what happened during that period, but there were issues. We ran some MTR tests but they were inconclusive; packet losses were random along the entire path. We conclude that the results for that period is a freak anomaly. If we look at the speed to Chicago (mean 110, SD 2.87), the network speed is generally consistent. If we disregard that freak anomaly period, we can see that network speeds to North America can mostly saturate the promised 1Gbps port speed.

Finally, we present the charts for our APAC servers.

powered by Advanced iFrame. Get the Pro version on CodeCanyon.

The see-sawing is not unexpected, given the vast distance between Germany and the APAC locations. The speeds to Singapore (mean 82.3, SD 29.0) is decent on average, although depending on the day and time, some bottle-necking may be experienced. If you are from Australia, tough luck. Both Perth (mean 15.1, SD 10.5) and Sydney (mean 17.3, SD 11.6) do not perform well.

Final words

It appears that the actual performance of our Nexus Bytes Ryzen NVMe REBOX1 lived up to expectation. There is ample evidence suggesting that Nexus Bytes has a very solid VPS management model. The CPU/RAM and disk performance are excellent AND consistent. It is no understatement to say that their VPS is likely to perform on par with or even better than low-end dedicated servers for most use cases, especially their beefier VPSes. We are impressed, and you should be too.

tl;dr: Shut up and take my money now!

Note: we have reached out to Nexus Bytes for their response to our LEBRE-X review because we believe that our reviewed providers should also have the opportunity to respond to our observations. We will publish their response in full if we receive any.

Response from Nexus Bytes’ management (Jan. 15th, 2020):

Thank you admin for sharing your detailed analysis. We are glad that this review validated our company’s philosophy: well-balanced nodes with healthy cpu : memory : storage ratio. Small hiccups may arise here and there; however, we try our level best to nip things in the bud and ensure our family members are receiving steady and consistent service, regardless of how much they paid.

We value our customers and treat them more as a family member and not just a mere customer. We are not flashy in our advertising nor do we offer unsustainable prices. If anything, we prefer to under-sell and over-deliver than the other way round, and we will continue to ensure that our family members who put their trust in us get nothing less than the best that we can offer.

Jay C., NexusBytes LLC