Yet it's the sysadmin who gets blamed, not the developer. "How can you tune the database so this doesn't happen?"
this post was submitted on 02 Mar 2024
13 points (100.0% liked)
Programmer Humor
35742 readers
150 users here now
Post funny things about programming here! (Or just rant about your favourite programming language.)
Rules:
- Posts must be relevant to programming, programmers, or computer science.
- No NSFW content.
- Jokes must be in good taste. No hate speech, bigotry, etc.
founded 5 years ago
MODERATORS
I am telling you this because hopefully it will make you feel a little better. Our head of it blames devs for slow queries.
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
So you are saying you are the expert in unshitifying queries? What is the most common thing that needs to be unshitified?
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"
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.
In my 30 years of experience, it is usually the devs.
As a dev, yes usually. It is certainly the better starting point.
At my job, it's almost always the dev team that is called first for bad DB performance (not always, because sometimes it is the server that's borked).
I'm the sysadmin (and transitioning to DevOps) at work, but the DBs are 100% in control of our two devs (one of which being the head of IT).
Apparently we're going to hire a third Dev, who will moonlight as our DBA -- oh, and for 30K/yr.
I'm sure this will go well.
Infinitely this, biggest pet peeve
Allergic to Indices? If your database is slow just add more Indices until you have one on every column of every table! :-)
Hi I need to add some data to the database.
No you fucking don't
So the guy died and decomposed in 10 minutes and somehow it mysql's fault?
10 minutes for a process is essentially infinity
Very big table, complex operations, much waiting, so yeah.
In this comic, bodily decomposition occurs at a "feels like" pace:-).
Poor guy got sigkill-ed, but MySQL keeps going with the request