azukaar / Cosmos-Server

☁️ The Most Secure and Easy Selfhosted Home Server. Take control of your data and privacy without sacrificing security and stability (Authentication, anti-DDOS, anti-bot)
https://cosmos-cloud.io
Other
3.45k stars 119 forks source link

[HELP]: High network usage of cosmos-server #142

Closed VictorEnaud closed 10 months ago

VictorEnaud commented 10 months ago

Hi, I just installed Cosmos Server today on my Raspberry, and everything was fine. I only added home-assistant, without doing nothing more (not even configuring it), and haven't changed setup configuration (where I added my domain and let's encrypt).

3 hours later, without doing anything, I noticed an uptick in network usage. In less than a hour, Cosmos-Server sent ~150Mb and received ~100Mb. While before it was only around ~1Mb for both.

Is it normal for Cosmos-Server to have such a high network consumption suddenly? I tried removing all automatic updates, rebooting the raspberry as well as the containers, to no avail.

azukaar commented 10 months ago

Cosmos network usage is always going to be very high, it is your reverse proxy. All the network of all your container will go throught Cosmos, it is quite natural to see high usage. You should be able to cross reference that network usage to other container's own usage (ex if you have 150mb on Cosmos you should have 150mb of total usage on the other containers) this is an example, here, I have 2.7gb on Cosmos, but that actually matches the sum of all the other container's network:

image

VictorEnaud commented 10 months ago

Thanks for the clarification. I did not see any correlation between the cosmos-server usage and the others containers usage.

I have much more usage on cosmos-server, than on all the others containers. :thinking: image

azukaar commented 10 months ago

In your screenshot Mongo has transmitted 120mb, Cosmos has received 135mb, that's where most of it come from (data from the queries to the DB)

then it transmitted 200mb which correspond to you previewing that DB data in the browser, guess you've been playing around with the dashboard a lot