I've been following @termer's post analyzing the leaks, but I haven't encountered any problems with it myself.
I have been running Jester+Httpbeast in production for a long time with heavy load, no problems at all, and no need for restarting the services, and no memory climbing. But I have changed over to mummy, which has proven better (for me) in many ways. Way lower compile time, no more async, etc. And also mummy has been in my production env for a long time now, and absolutely no problems. When comparing the different webservers please note that many of the benchmarks are just slamming data at them. The "real" benchmark should be based on your specific usecase - do you need to have blocking database calls? process calculations? etc. If you're just comparing the data slamming [benchmarks](https://github.com/guzba/mummy?tab=readme-ov-file#benchmarks), then all of them are pretty equal, and if the requests/sec is the blocker, scale your infrastructure. You could go for an easy solution with Wordpress or Shopify, but I think you should go for it with Nim :) ! Mummy + nimf-templates + vanilla CSS and JS ;)
