• brucethemoose@lemmy.world
    link
    fedilink
    English
    arrow-up
    0
    ·
    edit-2
    12 days ago

    Holy moly this is awesome! I am in for the 128GB SKU.

    That’s 96GB of usable VRAM! And way more CPU bandwidth than any desktop Zen chip.

    I know people are going to complain about non upgradable memory, but you can just replace the board, and in this case it’s so worth it for the speed/power efficiency. This isn’t artificial crippling, it physically has to be soldered, at least until LPCAMM catches on.

    My only ask would be a full X16 (or at least a physical X16/electrical x8) PCIe slot or breakout ribbon. X4 would be a bit of a bottleneck for some GPUs/workloads… Does Strix Halo even support that?

    • slacktoid@lemmy.ml
      link
      fedilink
      English
      arrow-up
      0
      ·
      12 days ago

      I understand the memory constraints but it does feel weird for framework, is all I have to say. But that’s also the general trajectory of computing from what it seems. I really want lpcamm to catch on!

      • brucethemoose@lemmy.world
        link
        fedilink
        English
        arrow-up
        0
        ·
        edit-2
        12 days ago

        Eventually most system RAM will have to be packaged anyway. Physics dictates that one pays a penalty going over pins and mobo traces, and it gets more severe with every advancement.

        It’s possible that external RAM will eventually evolve into a “2nd tier” of system memory, for background processes, spillover, inactive programs/data, things like that.

        • slacktoid@lemmy.ml
          link
          fedilink
          English
          arrow-up
          1
          ·
          2 days ago

          That would be fine. But as long as it can use it as RAM and not just a staging ground.

          • brucethemoose@lemmy.world
            link
            fedilink
            English
            arrow-up
            1
            ·
            2 days ago

            Keep in mind that it would be pretty slow, as it doesn’t make sense to burn power and die area on a wide secondary bus.

      • Nalivai@lemmy.world
        link
        fedilink
        English
        arrow-up
        0
        ·
        11 days ago

        Apparently AMD wasn’t able to make socketed RAM work, timings aren’t viable. So Framework has the choice of doing it this way or not doing it at all.

        • JcbAzPx@lemmy.world
          link
          fedilink
          English
          arrow-up
          0
          arrow-down
          1
          ·
          11 days ago

          In that case, not at all is the right choice until AMD can figure out that frankly brain dead easy thing.

          • alphabethunter@lemmy.world
            link
            fedilink
            English
            arrow-up
            1
            ·
            11 days ago

            “brain dead easy thing”… All you need is to just manage signal integrity of super fast speed ram to a super hungry state of the art soc that benefits from as fast of memory as it can get. Sounds easy af. /s

            They said that it was possible, but they lost over half of the speed doing it, so it was not worth it. It would severely cripple performance of the SOC.

            The only real complaint here is calling this a desktop, it’s somewhere in between a NUC and a real desktop. But I guess it technically sits on a desk top, while also being an itx motherboard.