IIRC you can get into the tens of microseconds with an x86 box running a heavy linux graphic desktop with real time patches. Single digits with core pinning on

IIRC you can get into the tens of microseconds with an x86 box running a heavy linux graphic desktop with real time patches. Single digits with core pinning on a light headless system. Bear in mind that real time performance and throughput are perpetually at odds with each other. Long story short, scheduling things such that everything happens in a tight time window means you need to leave gaps in the timeline. This tradeoff is variable so you can loosen requirements for running something like a rover where there isn't really all that much need for tight realtime control, it's not trying to achieve micron positioning as it drives around. That means you can use a more efficient CPU and lower your idle current which is probably the real constraint here.