Miscellaneous Aspects and Concluding Remarks

Networking and storage are aspects that may be of vital importance in specific PC use-cases. The ASRock NUCS BOX-1360P/D4 comes with the Wi-Fi 6E AX210 WLAN card that also include Bluetooth 5.2 support. On the wired front, we have a 2.5 Gbps port backed by the Intel I226-LM controller. A dual LAN option in this form-factor would have been nice to have, but consumers needing that can always go in for the full-height NUC BOX-1360P/D4. Strangely, the vPro support available in the NUC BOX-1260P seems to be absent here.

On the storage side, the NUCS BOX-1360P does have support for a PCIe 4.0 x4 NVMe SSDs (and we used one in our configuration). However, cooling those within the space constraints imposed by the form-factor of the slim NUC is very challenging, as we saw in the SSD temperature graph in the previous section. In the absence of an effective thermal solution, it might be a better option to stick with a PCIe 3.0 x4 NVMe SSD for this unit. From a benchmarking perspective, we provide results from the WPCstorage test of SPECworkstation 3.1. This benchmark replays access traces from various programs used in different verticals and compares the score against the one obtained with a 2017 SanDisk 512GB SATA SSD in the SPECworkstation 3.1 reference system.

SPECworkstation 3.1.0 - WPCstorage SPEC Ratio Scores

The graphs above present results for different verticals, as grouped by SPECworkstation 3.1. The storage workload consists of 60 subtests. Access traces from CFD solvers and programs such as Catia, Creo, and Soidworks come under 'Product Development'. Storage access traces from the NAMD and LAMMPS molecular dynamics simulator are under the 'Life Sciences' category. 'General Operations' includes access traces from 7-Zip and Mozilla programs. The 'Energy' category replays traces from the energy-02 SPECviewperf workload. The 'Media and Entertainment' vertical includes Handbrake, Maya, and 3dsmax. The gulf between the same SSD in the NUC BOX-1260P and the NUCS BOX-1360P would have been surprising if not for the fact that the new form-factor lacks airflow and cooling support for the SSD.

In pursuit of more investigation into the in-band ECC feature, I dug up one of the DDR4 SODIMMs that I had junked earlier for failing MemTest. Placing that in the system and running MemTest again on it delivered interesting results based on the chosen in-band ECC option. The following screenshots are from the display output recorded via a HDMI capture card - the timestamps in the video capture are to be noted.

PassMark MemTest Processing on Faulty SODIMM

With the default settings (in-band ECC turned off), the memory test reports failure in due course. On the other hand, with in-band ECC activated, MemTest ends up hanging - most likely after encountering the first memory error (before the testing program can get access to the faulty read data, the memory / ECC handling controller has detected uncorrectable errors and triggered an interrupt - which MemTest is probably unable to handle).

It appears that the in-band ECC has been present since Tiger Lake in a variety of processors. While its availability in the embedded processors line is clearly advertised on ark (example), its presence in the desktop (12th Gen. / 13th Gen.) and mobile (PDF) product line is buried under layers of documentation and not advertised widely. The murky aspect here is that error correction with standard DRAM is specified to be supported only in Chrome systems. It is not clear what is specific to Chrome (and not available or implementable in Windows and Linux) that enables it to take advantage of the in-band ECC feature. This is perhaps something worthy of follow-up by the open-source community, as the feature is of considerable interest to NAS operating systems.

Closing Thoughts

The ASRock NUCS BOX-1360P/D4 provided us with the opportunity to evaluate one of the first end products based on Intel's latest Raptor Lake-P platform. The product fulfills all our basic expectations from ASRock Industrial - we have seen that their UCFF systems run in a stable manner and provide good performance without much of an attempt at overall power consumption optimization. That trend continues with the NUCS BOX-1360P/D4. This approach has allowed ASRock Industrial to attract early adopters, and at the same time also target use-cases where the idle power consumption aspect is not much of a concern. The NUCS BOX-1360P/D4 is a worthy upgrade to the NUC BOX-1260P in terms of performance. On the I/O front, the trifurcation of the product line by ASRock Industrial has resulted in the need to wait for the other NUC BOX-1300 models if dual LAN and USB 3.2 Gen 2x2 capabilities are desired. Compared to their previous UCFF systems, the NUCS BOX-1300 series has a reduced height, and this does affect the thermal situation of the M.2 SSD. Hopefully, ASRock Industrial can address this with a solution similar to the one employed by Intel in their slim NUC kits.

Intel's Raptor Lake-P is quite close to Alder Lake-P architecturally. The core counts, cache sizes, and heterogeneous combinations are pretty much equivalent. Under such circumstances, it is indeed surprising that just process advancements have enabled Raptor Lake-P to provide satisfactory improvements in performance as well as power efficiency over Alder Lake-P. We are able to reach this conclusion despite evaluating a system that has not yet been optimized for power based on the energy consumption numbers for key UCFF PC workloads. A comparison of the power consumption profile of the NUC BOX-1260P and the equivalent Wall Street Canyon NUC shows that ASRock Industrial leaves plenty on the table for further optimization.

The expected generational improvements aside, it is heartening to see in-band ECC support getting more visibility. The ability to improve upon memory integrity without having to spring for special types of RAM or additional board area / traces can be a major selling point in a variety of consumer applications also. We are hopeful that Intel will not restrict it to industrial and embedded SKUs alone. On Raptor Lake-P specifically, we hope Intel will help enable it on operating systems beyond just Chrome OS. Obviously, there is no free lunch, and we do see some loss in performance for specific workloads (such as ones involving heavy iGPU activity). In situations requiring memory protection, the delta is not big enough to be a deal-breaker.

ASRock Industrial plans to market the NUCS BOX-1360P/D4 at a price point similar to the NUC BOX-1260P - $700 (Update: USD 691 at launch on February 7, 2023). Given the performance improvements over the previous generation NUC BOX-1260P as well as other UCFF systems, and the new features enabled in Raptor Lake-P, the pricing is justified. We look forward to the company optimizing the BIOS to address the idle power consumption issue, and tag on an appropriate thermal solution for the M.2 SSD. Those minor quibbles aside, the product is on completely solid ground in terms of both price and performance.

Power Consumption and Thermal Characteristics
Comments Locked

30 Comments

View All Comments

  • drajitshnew - Sunday, January 29, 2023 - link

    The in band ECC is an absolutely brilliant idea for systems with 64 GB or more. It is unfortunate that windows does not support it.
  • Samus - Sunday, January 29, 2023 - link

    My understanding is this doesn't need support at the software level. This is still "hardware ECC" and OS-independent.
  • Samus - Sunday, January 29, 2023 - link

    Oh, I see what you are saying. About how Windows will handle an error. In AT's memtest run the test triggered a stop interrupt presumably as it didn't know how to handle the error. I see what you are getting at with Windows.
  • bernstein - Monday, January 30, 2023 - link

    it's more likely, that chrome mandates ecc support, while with windows intel pushes ecc as $$$ feature
  • sjkpublic@gmail.com - Monday, February 13, 2023 - link

    This competes with laptops. Please expand on why ECC is coming up?
  • mode_13h - Tuesday, February 14, 2023 - link

    > Please expand on why ECC is coming up?

    This is sold as an industrial mini-PC. For something like that, reliability is key. Memory errors are one potential source of reliability problems, and ECC is an effective measure to compensate (short-term) and flag for replacement (long-term) any defective memory modules or boards.

    The lore behind ECC is that it protects against cosmic rays, but I've only personally seen ECC errors that seem tied to flaky or failing hardware. It's worthwhile even for that purpose, alone.
  • TLindgren - Sunday, January 29, 2023 - link

    It needs to be noted that SECDED over 512 bit is FAR less powerfull in handling errors than SECDED over 64-bit like regular ECC (or SECDED over 32-bit using DDR5 ECC sticks). They could have instead emulated the SECDED over each 64-bit chunk but then the extra reserved memory would have needed to be 8GB instead of 2GB, and the performance penalty likely would have been sigificantly worse.
    SECDED means it's guaranteed to correct one incorrect bit (SEC) and detect two incorrect bits (DED), no warranties for what happen with more incorrect bits but there's a decent statistical chance it'll detect them (but no chance it'll fix them).
    Obviously getting two or even three+ faulty bits in the same "group" is far more likely over 512-bit compared to 64-bit, in fact it's my understanding that it'll likely happen most of the time given how memory sticks are constructed!
    It's still useful because it'll detect a certain percentage of the multi-bit error so you will often? get told that you that you have faulty memory (except this doesn't seem to work) before things crash which means you know you need to fix the hardware, but the "correct bits" part is unlikely to save you because at least some of the time it'll get multiple wrong bits in the burst. I suspect they would have been better of with just giving up on correcting and aiming for "detect as many bit errors as we can" (probably 3-4 guaranteed bit detected with the 16-bit of extra data per 512bit they choose).
    It's definitely better than no ECC *if* the software support gets improved a bit, but is in no way comparable to "real" ECC. OTOH, it's not priced as that either but it needs to be pointed out because some people will sell it as if it is.
  • ganeshts - Monday, January 30, 2023 - link

    Taken standalone, you arguments are completely sound.

    However, in the bigger picture, you should note that newer memory technologies include link ECC to protect the high-speed communication link between the SoC and the external memory, AND, the DRAM DIMMs themselves implement transparent ECC for the stored data.

    Overall, even mission-critical requirements like ASIL / ISO26262 (for automotive safety) can be met with the requisite FIT (failure-in-time) rate using SECDED protection for 512-bit blocks *assuming those other protection mechanisms are also in place*.

    In-band ECC is also used on Tegra for such embedded applications [ https://twitter.com/never_released/status/13559704... ; I can't seem to dig up the original documentation, but remember this was heavily discussed when the Tegra feature was made public ].
  • ganeshts - Monday, January 30, 2023 - link

    (Correction: DRAM DIMMs -> The memory chips)
  • mode_13h - Tuesday, February 14, 2023 - link

    > you should note that newer memory technologies include link ECC to protect the high-speed communication link between the SoC and the external memory

    Are you saying the system you reviewed also supports traditional out-of-band ECC? Why wasn't that mentioned in the review? If not, then your point would seem to be moot.

    I also don't see the point of using in-band ECC atop OOB ECC. Anything that OOB ECC can't correct doesn't seem like it's going to be correctable by in-band ECC.

Log in

Don't have an account? Sign up now