980
muskrat's data eng expert's hard drive overheats while processing 60k rows (lemmy.dbzer0.com)
submitted 2 years ago by to c/programmer_humor@programming.dev
292 comments fedilink hide all child comments
 
you are viewing a single comment's thread
view the rest of the comments
[–] 9 points 2 years ago (6 children)

Hard drives do get hot and need some cooling but not at 60k rows. Its either made up or their computer case is made of thermal cladding

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 6 child comments
    •
  • [–] 10 points 2 years ago (3 children)

    You could query 60,000 rows on a low tier smart phone. Makes no sense at all.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 3 child comments
    •
  • [–] 4 points 2 years ago (2 children)

    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...

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 2 points 2 years 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.

  • permalink
  • fedilink
  • source
  • parent
  • [–] 9 points 2 years ago* (1 child)

    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

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •
  • [–] 1 point 2 years 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.

  • permalink
  • fedilink
  • source
  • parent