Open carniz opened 6 years ago
Japronto yet not stable or somewhere active productive things, Don't think to use for production. yet pending issue and similar your reported issues we faced too.
Let's make japronto stable so that it can be used for production. Honestly, I already use it and I hope that the author will be able to fix bugs with our help.
We also interested to use it, but don’t trust until dedication brings on open version.
@carniz Could you check file description count of suthost_1 container? I think a reason is socket reuse
@squeaky-pl I'm using Japronto in production, but when I changed my code to work with more than one worker_num
, I started to memory leak issues. Using one worker there is no issue even after months of work and I monitor the AWS instances very carefully via CloudWatch.
I really hope you can look into this issue. If you can create a PR I will test it and let you know if the issue has been resolved.
I'm trying out japronto 0.1.1, and I have a small app looking like this:
It is docker-composed together with a wiremock-container, which is stubbed like this:
curl -X POST --data '{ "request": { "url": "/get/this", "method": "GET" }, "response": { "status": 200, "body": "Ecco ci\n" }}' localhost:8080/__admin/mappings/new
I then run apache-bench like this:
ab -n 10000 -c100 localhost:9090/wiremock
The first run, it completes in 9.2 seconds:
The second run, it completes in 13.5 seconds:
The third time, it doesn't complete:
The docker-compose logs reveals the following:
What could be the reason for this? (memory leak, or something else?)