3 ms·
If you want to build scalable software, this is the only line you need from this blog post: > You need to schedule few thousand record samples and monitor how
by albertgoeswoof 3y ago
If you want to build scalable software, this is the only line you need from this blog post:
> You need to schedule few thousand record samples and monitor how well/bad will your worker perform
I find it staggering how many senior developers don’t know how to profile or performance test their software. Just throwing a few million rows into a local db and measuring your app performance is so basic, yet I’ve seen many teams not even consider this, and others farm it to a “QA”.
- inferiorhuman 3y agoI've seen two things that prompt this behavior: - Fear of the database. For some folks keeping the logic in the app which is fully under their control is comforting. I find this to be common by folks who've been burnt by their db in the past. It's a lot easier to assert (quality) control over your own software. - Difficulty in modeling data. This is more tricky, but IMO separates code monkeys from developers.
- what-no-tests 3y agoYes - often what once worked when the application only had a few hundred or thousand records doesn't work anymore, now that it has millions of records. Those milliseconds, N+1 queries, nested queries, large joins (owing to incongruence between logical data structure and how that data is stored on disk) and poorly-indexed tables combine into lots of sad times.