4 ms·
Thank you! You gave me a great term that I can jump off from (NIF). I'll have to rig up Observer. I've been using recon because I was being lazy overall.
by madamelic 2y ago
Thank you! You gave me a great term that I can jump off from (NIF).
I'll have to rig up Observer. I've been using recon because I was being lazy overall.
- gregors 2y agoOnce upon a time I needed to do hashes en masse for a specific blockchain projects. Just a tad of Rust (via nif) really helped the performance. Might be of help to you, check this out (not my lib) https://github.com/ExWeb3/ex_keccak https://github.com/ExWeb3/ex_keccak for my usage, benchmarks went from 2.79K ips to 346.97K ips
- elcritch 2y agoYou might also look into Elixir's broadway as provides back-pressure [1]. 1: https://hexdocs.pm/broadway/Broadway.html https://hexdocs.pm/broadway/Broadway.html > I also looked into the wake-up lengths of threads. I am starting to get my head around "dirty schedulers" but I am not entirely sure how to affect those or how I can besides it doing it forever me. Note that dirty schedulers really only affect NIFs which run longer than what the BEAM schedulers expect. I mentioned that in regards the possibility that the AWS sigs are taking longer than they should, then they'd cause havoc on the scheduler.