linuxcnc 2.9.2 (live) on the intel n100 cpu

I recently got a n100 mini-pc. Specifically the Firebat T8 Plus from aliexpress.
It comes with an intel n100 cpu, 512g nvme ssd,16g ddr5 ram, dual gigabit lan ports, wifi & BT. all working out of the box with the linuxcnc 2.9.2 live iso.
Attached is the latency test I ran. Youtube was also playing at 1080p in the background.
Priced at about the same as a pi5 (or even cheaper) and with better specs. Also cheaper, smaller and less power hungry than building a new PC.
Seems like the way to go right now for Mesa card users.



 

Pretty bad? I thought it was good result. This is perfectly fine for use with a mesa card in my experience.

Dunno if it's bad but certainly not what you'd expect from a Q1 '23 Intel 4-cores 6mb cache release for sure. Wtf went wrong with Intel... pretty sure we'll all be scoring superior processing pwr with Chinese RISC-V for twice less in a year at this down-slope rate. 

For comparaison here's an ice-age medieval antiquated expired dual core $15.00 PC a.k.a. worst performer I can find in the shop atm. 

Mind doing this all over again? But with the following isocpus. I'd really appreciate it because I'm actually looking into those dual-ethernet industrial PC myself at this very moment. Although I was advised by a Lcnc hardware seller to score an Intel J6426 (for whatever reason he had, I wouldn't know). The N100 is also an option but rather questionable after seeing your perf. Try isolating 2 cores and give it a chance, that'd be cool. Thanks.

Results looks about the same to me.
Actually a little worse with the core isolation(62.2us). The second image (33.6us) is which a bunch of stuff disabled in the bios as tommylight suggested. Probably not everything. Speedstep, virtualization, c-states have been disabled.



 

Nothing makes any sense at all. I appreciate the effort in showing us how to avoid the N100 at all cost, future Intel silicon releases also...  

Not impressed. Decided to keep my ice-age core-duosaur for another decade (century, ideally). Thanks and all the best. 

Ah snap, I forgot to add those twentysiz million glxgears in. Near death and crawllin like a snake. Go figure... 
Bet I'll set the shop on fire if I attempt this with intel's newly cut-corner range of nothing.

Isn't your pursuit somewhat of a wild goose chase? You're only running a servo thread so I'm assuming you have a hardware motion controller like a mesa card, and if that's the case, is there any benefit to having 20us max jitter vs 60 or even 80? I'm sure someone more knowledgeable will correct me if I'm wrong, but with a mesa board even 100us max jitter should be fine. In the context of linuxcnc (and real-time in general), it's more of a "works/doesn't work" rather than "this works faster".

I'm actually quite please with this computer. There are multiple threads here struggling with just the right raspberry pi config with a custom linuxcnc image, or threads about other SBCs working with linuxcnc at all - orange pi, banana pi, odroid and so on, while this one seems to work just fine out of the box with the regular x86 image. No messing about.

I'll do as tommylight suggested and run it overnight soon so we'll see, but that puts us back to the works/doesn't work thing. if it works fine with high jitter, it really doesn't matter that other cpus can do the same job with lower jitter, no?