12
Replacing a 3 GB SQLite database with a 10 MB FST (finite state transducer) binary (til.andrew-quinn.me)
submitted 6 months ago by to c/programming@lemmy.ml
4 comments fedilink hide all child comments
you are viewing a single comment's thread
view the rest of the comments
[–] 1 point 6 months ago (1 child)

essentially they were using a database that needed much more than what they required which made everything super slow, so they used a more precise and small tool for the job they needed exactly, reducing the db's size. am i correct? i've been touching on this topic a bit recently so it's all still very new to me.

  • permalink
  • fedilink
  • source
  • hideshow 1 child comment
    •
  • [–] [S] 3 points 6 months ago

    Yup, that basically sums it up. The key part though was that doing the inefficient thing first allowed them to make progress and to understand the problem better by working through it, which later led to a more clever solution. The moral of the story here is that it's always better to solve the problem even if your solution isn't optimal, and then reflect on it.

  • permalink
  • fedilink
  • source
  • parent