• @[email protected]
    link
    fedilink
    2310 months ago

    I am telling you this because hopefully it will make you feel a little better. Our head of it blames devs for slow queries.

    • @lightnegative
      link
      310 months ago

      Devs who don’t understand how SQL or relational databases work write absolute abortions of queries.

      9 times out of 10 - yes it is absolutely the devs. I say that as the dev who gets tasked with analysing why these shitty queries from our low budget outsourced labour are so slow

      • @[email protected]
        link
        fedilink
        410 months ago

        So you are saying you are the expert in unshitifying queries? What is the most common thing that needs to be unshitified?

        • @lightnegative
          link
          410 months ago

          Err, no? At what point did I claim to be an expert?

          It doesn’t take a genius to realise that serving 100-record chunks of a billion record dataset using limit 100 offset 582760200 is never gonna perform well

          Or that converting indexed time columns to strings and doing string comparisons on them makes every query perform an entire table scan, which is obvious if you actually take the time to look at the query plan (spoiler: they don’t)

          “Why can’t the system handle more than 2 queries per second? This database sucks”

          • @[email protected]
            link
            fedilink
            310 months ago

            I didn’t mean it so serious. I just tried to express that you seem to have experience with it and I am wondering what you have to deal with. I am sorry if it came across negatively.