• mycodesucks@lemmy.world
    link
    fedilink
    arrow-up
    6
    ·
    28 days ago

    In that guy’s defense, you as a user have EVERY right to be pissed if your machine thrashes so badly that your system stops responding in an era of 32 Gb of RAM and 8 core CPUs.

    • CaffeineMan@lemmy.ml
      link
      fedilink
      arrow-up
      2
      ·
      28 days ago

      We had a mainframe that, because user IO was a higher priority than background jobs, would slowdown the server by a user treating the F5 button like he was in a competition playing Track and Field in the televised 100m dash event while waiting for work to populate. That system was well over 32gb of ram with many more than 8 cores.

      We had to talk to him.

  • friend_of_satan@lemmy.world
    link
    fedilink
    English
    arrow-up
    5
    ·
    28 days ago

    In tech support we called the mouse the “math coprocessor”, and any interactions with it sped up all computation.

  • Trail@lemmy.world
    link
    fedilink
    arrow-up
    3
    ·
    28 days ago

    Could be low system entropy while generating a hash or key and the mouse input is helping it.

    There was some program that was asking you to move the mouse while it was generating a seed or something, but I don’t remember which one.