• spooky2092@lemmy.blahaj.zone
    link
    fedilink
    English
    arrow-up
    57
    ·
    19 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
      30
      ·
      edit-2
      19 hours 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.

      • T156@lemmy.world
        link
        fedilink
        English
        arrow-up
        2
        ·
        edit-2
        8 hours ago

        In my experience, the only time that I’ve taxed a drive when doing a database query is either when dumping it, or with SQLite’s vacuum, which copies the whole thing.

        For a pretty simple search like OP seems to be doing, the indices should have taken care of basically all the heavy lifting.

    • AThing4String@sh.itjust.works
      link
      fedilink
      arrow-up
      16
      ·
      19 hours 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
      2
      ·
      edit-2
      18 hours ago

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