Out of memory/overheating in 60k rows? I've had a few multi-million row databases that could fit into a few gigs of memory, and most modern machines have that much in RAM. A 60k query that overheats the machine might only happen if you're doing something weird with joins.

Plus a lot of reads is nothing really, for basically all databases, unless you're doing an unsmart thing with how you're reading it (like scanning the whole database over and over). If you're not processing the data, it'd be I/O bottlenecked.

[–] KillingTimeItself@lemmy.dbzer0.com 2 points 23 hours ago

if they wrote good code yeah, evidently they didn't write good code if they're struggling to process 60k lines of a database lmao.

They must either be O(n^10) complexity or something retarded like that for this to be the case. I wouldn't put it past them.

Plus a lot of reads is nothing really, for basically all databases, unless you’re doing an unsmart thing with how you’re reading it (like scanning the whole database over and over). If you’re not processing the data, it’d be I/O bottlenecked.

again, i'm assuming they aren't very smart, since this is an issue in the first place.