• Mniot@programming.dev
        link
        fedilink
        English
        arrow-up
        4
        ·
        13 hours ago

        Can we think of any device someone might have that would struggle with 60k? Certainly an ESP32 chip could handle it fine, so most IoT devices would work…

        • T156@lemmy.world
          link
          fedilink
          English
          arrow-up
          1
          ·
          6 hours ago

          Unless the database was designed by someone who only knows of data as that robot from Star Trek, most would be absolutely fine with 60k rows. I wouldn’t be surprised if the machine they’re using caches that much in RAM alone.

        • zenpocalypse@lemm.ee
          link
          fedilink
          English
          arrow-up
          4
          ·
          13 hours ago

          Right? There’s no part of that xeet that makes any real sense coming from a “data engineer.”

          Terrifying, really.

    • xthexder@l.sw0.com
      link
      fedilink
      arrow-up
      9
      ·
      edit-2
      14 hours ago

      Imo if they can’t max out their harddrive for at least 24 hours without it breaking, their computer was already broken. They just didn’t know it yet.

      Any reasonable SSD would just throttle if it was getting too hot, and I’ve never heard of a HDD overheating on its own, only if there’s some external heat sources, like running it in a 60°C room

      • T156@lemmy.world
        link
        fedilink
        English
        arrow-up
        1
        ·
        6 hours ago

        Hard Drives might do it if the enclosure is poorly designed (no ventilation), but I can’t imagine a situation where it would overheat like that that quickly, even in a sealed box. 30k is nothing in database terms, and if their query was that heavy, it would bottleneck on the CPU, and barely heat the drive at all.