home.social

#inorder — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #inorder, aggregated by home.social.

  1. #This is just a #PassingThought; #IT's of #NoConsequence, #OneWay or #Another...

    #InOrder to #Qualify as a crappy little #PopVideo; don't you have to be #Popular - #AtTheVeryLeast...

    #Nope... #IGuessNot...

    A #CrappyLittlePopVideo is #Still a #CrappyLittlePopVideo even when #NoOne #SeesIT...

    🧙⚔️​🤖🐺🤖⚔️​🧙 | 💀​​🦹🧟​🦄​​​​🧟​🦹💀

  2. #YippitySkippity; we're #OilChangeReady...

    #IT's #One of #MyFavouriteChores...

    #InOrder to be #OilChangeReady; #One will "need":

    #Stuff;
    #Things;
    #Oil; and,
    #Things that need an #OilChange

    • And, #Biscuits

    #RedBeanBearSaysSo

    #YoureWelcome

    #HaveSomePizza

    🧙🍕​​🤖🐺🤖🍕​🧙 | :fediverse:​🦹🍪​​🐻​🍪​🦹:fediverse:

  3. @m20k #inorder+#prefetch is fantastic for energy efficiency, but #OoO’s flexibility in the face of cache misses and #branchmissprediction leads to much better performance for many workloads. By “scaling” I meant scaling to higher performance with wider issue, requiring even better BP accuracy and covering for even longer #cachemiss penalties.

    We can do better than scaling this instruction-at-a-time model we have been using since the 1950es, but that’s for another toot.

  4. @m20k #inorder+#prefetch is fantastic for energy efficiency, but #OoO’s flexibility in the face of cache misses and #branchmissprediction leads to much better performance for many workloads. By “scaling” I meant scaling to higher performance with wider issue, requiring even better BP accuracy and covering for even longer #cachemiss penalties.

    We can do better than scaling this instruction-at-a-time model we have been using since the 1950es, but that’s for another toot.

  5. @m20k #inorder+#prefetch is fantastic for energy efficiency, but #OoO’s flexibility in the face of cache misses and #branchmissprediction leads to much better performance for many workloads. By “scaling” I meant scaling to higher performance with wider issue, requiring even better BP accuracy and covering for even longer #cachemiss penalties.

    We can do better than scaling this instruction-at-a-time model we have been using since the 1950es, but that’s for another toot.

  6. @m20k #inorder+#prefetch is fantastic for energy efficiency, but #OoO’s flexibility in the face of cache misses and #branchmissprediction leads to much better performance for many workloads. By “scaling” I meant scaling to higher performance with wider issue, requiring even better BP accuracy and covering for even longer #cachemiss penalties.

    We can do better than scaling this instruction-at-a-time model we have been using since the 1950es, but that’s for another toot.