I think the key word here is "you".

You just get it running, hack your spaghetti and when it becomes a problem you're already assigned on another project so someone else will have to sort it out.

And that guy is usually me.

Just remember when you leave a pool of shit behind, one of the victims might be making a hiring decision about you at some point in the future.

Read that last part again folks. Twice if you have to. You will run into the same folks in the industry if you last longer than 10 years.

“The industry” extends far beyond and is more than the big tech circle jerk. I’ve bounced around outside of the big tech circus for nearly 15 years now and have -never- unwittingly run into someone I previously worked with. Have I targeted institutions that I know employ people that I've crossed paths with in the past? Yes, deliberately for one reason or another, but never once have I been hired, paged through a company directory and been surprised to the point of "oh, they're here?".

Hey man if I run into the same people again I hope they either understand what my situation was.

People try to do their best.

So... throw money on compute instead of just adding an index..?

Seems Kubeblocks provids some parameters templates based on their knowledge on databases. To some extent, it will improve performance. Of course, I don't think users will be totally freed from `database tuning`, which is too complex a topic.

I’m offended that you don’t take even 10 minutes to understand why this will not work.

People say they don't need sysadmins and stuff like this is the result.

Vertical scalability limits are very soon met and can be difficult to fix post-fact.

My scepticism was clearly not well enough signalled, apologies.

To be clear I agree "waste money to avoid applying basic database techniques" is A Bad Thing!

It's phrased as a joke, no?

This works when your data fits in L2 cache

https://www.sqlite.org/pragma.html#pragma_optimize ?

If SQLite feels that performing database optimizations (such as running ANALYZE or creating new indexes) will improve the performance of future queries, then some database I/O may be done.

Try it and maybe you get a dream-come-true.

Lol glad I’m not the only one who immediately thought “bullshit” when reading that.

At best it becomes someone else’s problem, as others here have said.