๐— ๐—ฒ๐—บ๐—ผ๐—ฟ๐˜† ๐—ถ๐˜€ ๐˜๐—ต๐—ฒ ๐—ฏ๐—ผ๐˜๐˜๐—น๐—ฒ๐—ป๐—ฒ๐—ฐ๐—ธ

AI silicon isnโ€™t compute-bound anymore.ย Itโ€™s memory-bound.

In several recent conversations (including around @ChipStartUK / Silicon Catalyst UK), one point kept coming up:
๐—”๐—œ ๐˜€๐˜†๐˜€๐˜๐—ฒ๐—บ๐˜€ ๐—ฎ๐—ฟ๐—ฒ ๐—ป๐—ผ๐˜„ ๐—ฑ๐—ผ๐—บ๐—ถ๐—ป๐—ฎ๐˜๐—ฒ๐—ฑ ๐—ฏ๐˜† ๐—บ๐—ฒ๐—บ๐—ผ๐—ฟ๐˜†; ๐—ผ๐—ณ๐˜๐—ฒ๐—ป ๐—บ๐—ผ๐—ฟ๐—ฒ ๐˜๐—ต๐—ฎ๐—ป ๐—ต๐—ฎ๐—น๐—ณ ๐˜๐—ต๐—ฒ ๐˜€๐˜†๐˜€๐˜๐—ฒ๐—บ.

Memory scaling has effectively stalled at ~16nm. That changes everything, making the real problem now is:

  • moving data efficiently
  • managing bandwidth
  • controlling energy per bit

You see the same theme coming through in SemiEngineering and EE Times, the energy cost of data movement is overtaking compute so we are optimising data low flow and not just logic.

Physical implementation execution becomes a real differentiator efficiently moving and managing data at silicon level.

Read more in this EETimes article – โ€œ๐—ช๐—ต๐˜† ๐— ๐—ฒ๐—บ๐—ผ๐—ฟ๐˜†, ๐—ก๐—ผ๐˜ ๐—–๐—ผ๐—บ๐—ฝ๐˜‚๐˜๐—ฒ ๐—ช๐—ถ๐—น๐—น ๐——๐—ฒ๐—ฐ๐—ถ๐—ฑ๐—ฒ ๐˜๐—ต๐—ฒ ๐—™๐˜‚๐˜๐˜‚๐—ฟ๐—ฒ ๐—ผ๐—ณ ๐—”๐—œโ€

This entry was posted in Blogs. Bookmark the permalink.

Leave a Reply

Your email address will not be published. Required fields are marked *