Closed xmflsct closed 2 years ago
Hello, how many proxy clients do you have? Is it freqtrade bots or something else?
Not so many, it was around 10-11 freqtrade instances running. I have another VM which runs perfectly with 18 freqtrade instances. I suspect it is because of pairs not clients?
It's because of amounts of requests, so the limit has to be increased.
Has proxy crashed?
No, the proxy did not crash, at least not from Docker's point of view.
The situation just appeared on my other VM which hosts that 18 freqtrade instances. Very weird. Don't know how to properly reproduce the situation. Will monitor a bit further.
fastHttp server has its own connection pool with a 1024*256 connection limit. So I will make it configurable in the next release
Thanks! What is a reasonable amount to set? 1024*256 seems already high, but not sure how many to count for each instance?
Actually, I don't know, so I recommend you increase that twice until the issue would not occurs. Also, it's could be an issue with freqtrade HTTP client that does not close connections in time.
What is the output of "ulimit -n"?
ulimit -n
In which context?
On your Linux instance
On the Linux VM, the result is 1024
.
In the docker container that runs freqtrade instance, the result is 1048576
.
What is the output of sudo lsof -Pi -p $PROXY_PID
? From your host
Also, I suggest checking the amount of opened file descriptions on your instance - https://www.cyberciti.biz/tips/linux-procfs-file-descriptors.html
sudo lsof -Pi -p $PROXY_PID
shows a long list.
The total count currently is 222
.
Getting
How to increase concurrency? Thanks!