Microsoft HoloLens: HPU Architecture, Detailed

Status
Not open for further replies.
Thanks for the update.

Initially, Microsoft didn’t want any one compute node utilized more than 50%, so there should be plenty of headroom built into the HPU for more taxing algorithms, thereby future-proofing the HoloLens as much as possible.

The company also specified exacting latency and duty cycle requirements, intended to reasonably assure the best experience possible.
In order to satisfy realtime latency requirements, they need to leave some headroom. So, they can't just double the workload and still hit their latency targets.

To me, the 1 GB of for the Atom cores seems like the weakest spec. This thing has to run Windows 10, their graphics stack, their AR stack, and the AR app, itself. For all that, 1 GB seems tiny.
 
Bit - the HPU does a lot of the heavy lifting and that has it's own RAM. Also although it's running Win10, it's not configured the same. The memory footprint is greatly reduced, anything not needed isn't running.
 
Even if you strip down Win 10 to the minimum, once you add back in the stuff needed for AR + apps, it seems like 1 GB ought to be a squeeze.

I'm confident they'll add more RAM, in the next version. Maybe that'll even be something I can afford!

Hopefully, it'll also use Broxton, based on Intel's Goldmont core, which is allegedly 50% faster per clock. That also has Gen9 HD Graphics (up to 18 EUs, I think).
 
Status
Not open for further replies.