Retrospectively Reverse-Engineering Apple's Neural Engine

(eiln.github.io)

50 points | by zdw 1 hour ago

3 comments

  • CraigJPerry 17 minutes ago
    This isn't ai slop. It's fascinating and well written.

    But I learned something really basic - i didn't know that the ANE (and the data pipeline around it) was designed for CNN rather than transformers. It's always been an open loop in my head, wondering why the ANE was less impactful than i understood it should be.

    • riedel 4 minutes ago
      A lot of neural engine, particularly in the embedded domain (ARM/RISC MCUs) have the same problem. Designing other models means on top of this means a lot of profiling to get convolution blocks right to get good speedups. (We optimized this in the past e.g. using Neural Architecture Search on super networks)
    • msdz 6 minutes ago
      > But I learned something really basic

      Same for me!

      Also, just imagine being the group at Apple responsible for designing this section of the chip, starting probably almost a decade back – under the constant uncertainty of not knowing what direction ML workloads would develop in…

  • LoganDark 37 minutes ago
    > what workloads it was designed for and accels at.

    excels!

    • pbhjpbhj 19 minutes ago
      Could've been a pun as a neural processor is an accelerator, so it 'accels' at machine learning tasks!
    • osquar 33 minutes ago
      At least we know it wasn't written by a bot
  • rima_667 1 minute ago
    [flagged]