Closed meower1 closed 1 month ago
could you run htop or something to track down the procress?
this is htop's results filtered to "snidust". the cpu pressure hasn't began yet as i've just started the process and it often starts a few hours after execution
okay sorry, instructions were a bit unclear....i meant to run htop or similar inside container when the cpu usage is that high
yeah i'll try to replicate the behavior on a spare server
this is the top
results from within the container after about a week of having the container running
output of docker stats
and this is the top
results from the first day i ran the container
output of htop
outside of the container on the host machine
so in short the first few days i've ran it i've had no issues with it whatsoever and it ran normally consuming a reasonable amount of resources and it gradually increases the resource usage after a while. restarting the container temporarily solves the issue
so it seems to be a nginx thing. i applied some changes....(no clue if it helps or make things worse to be honest)
However, i guess if my general use config is not working / scaling for your amout of traffic, you should link your own which optimized for your hardware
no worries ill test the new update and post the results here.
you should link your own which optimized for your hardware
im not sure i understand could u clarify this
i mean for example you need to set the nginx workers from auto
to 16
In this case you can just link your own optimized nginx config:
version: '3.3'
services:
snidust:
container_name: snidust
environment:
- 'ALLOWED_CLIENTS=127.0.0.1, 10.111.123.7'
- EXTERNAL_IP=10.111.123.8
ports:
- '443:8443'
- '80:8080'
- '53:5300/udp'
volumes:
- '~/mysuperchargednginx.conf:/etc/nginx/nginx.conf:ro
image: 'ghcr.io/seji64/snidust:1.0.14'
Hi again, I've been running the container for about a week and the performance issue seems to have been fixed. Thanks for the awesome project and the quick fix 🙌 ❤️
Hi, so i've setup the project on my private server with the following specs
and snidust seems to be consuming an unreasonable amount of resources specially cpu. it happens after a period of time has passed which im unsure of.
heres the output of docker stats
there is currently no user on the dns server other than myself
output of docker logs snidust
my docker compose file:
this has been the case for a while and had happened to me a bunch of time with this project i didn't have the time to report it tho.
thanks for the amazing project tho hoping to see this fixed in the future <3