• zalgotext
    link
    fedilink
    arrow-up
    61
    arrow-down
    1
    ·
    2 hours ago

    my hard drive overheated

    So, this means they either have a local copy on disk of whatever database they’re querying, or they’re dumping a remote db to disk at some point before/during/after their query, right?

    Either way, I have just one question - why?

      • spooky2092@lemmy.blahaj.zone
        link
        fedilink
        English
        arrow-up
        33
        ·
        2 hours ago

        Plus, 60k is nothing. One of our customers had a database that was over 3M records before it got some maintenance. No issue with overheating lol

        • surph_ninja@lemmy.world
          link
          fedilink
          arrow-up
          17
          ·
          edit-2
          58 minutes ago

          I run queries throughout the day that can return 8 million+ rows easily. Granted, it takes few minutes to run, but it has never caused a single issue with overheating even on slim pc’s.

          This makes no fucking sense. 60k rows would return in a flash even on shitty hardware. And if it taxes anything, it’s gonna be the ram or cpu- not the hard drive.

        • AThing4String
          link
          fedilink
          arrow-up
          4
          ·
          44 minutes ago

          I literally work with ~750,000 line exports on the daily on my little Lenovo workbook. It gets a little cranky, especially if I have a few of those big ones open, but I have yet to witness my hard drive melting down over it. I’m not doing anything special, and I have the exact same business-economy tier setup 95% of our business uses. While I’m doing this, that little champion is also driving 4 large monitors because I’m actual scum like that. Still no hardware meltdowns after 3 years, but I’ll admit the cat likes how warm it gets.

          750k lines is just for the branch specific item preferences table for one of our smaller business streams, too - FORGET what our sales record tables would look like, let alone the whole database! And when we’re talking about the entirety of the social security database, which should contain at least one line each in a table somewhere for most of the hundreds of millions of people currently living in the US, PLUS any historical records for dead people??

          Your hard drive melting after 60k lines, plus the attitude that 60k lines is a lot for a major database, speaks to GLARING IT incompetence.

        • Korhaka@sopuli.xyz
          link
          fedilink
          English
          arrow-up
          1
          ·
          edit-2
          2 minutes ago

          Pretty sure I run updates or inserts that count over 60k fairly often. No overheats. Select queries sometimes way higher.

      • Dave.@aussie.zone
        link
        fedilink
        arrow-up
        8
        arrow-down
        1
        ·
        1 hour ago

        You’ve got it all wrong, in traditional computer terminology the “hard drive” is the box that sits under the desk that collects cat fluff and cigarette tar.

        /s …?

    • Bosht@lemmy.world
      link
      fedilink
      English
      arrow-up
      3
      ·
      11 minutes ago

      I’d much sooner assume that they’re just fucking stupid and talking out of their ass tbh.

    • Adalast@lemmy.world
      link
      fedilink
      arrow-up
      4
      arrow-down
      1
      ·
      1 hour ago

      Why? Because they feel the need to have local copies of sensitive financial information because… You know… They are computer security experts.