I tried to delete and recreate the container, but there's still this insane power consumption.
For comparison, cloudflared doing a tunnel to hundreds of users takes 0.06% of CPU time on the same server
this post was submitted on 22 Jul 2023
39 points (97.6% liked)
Selfhosted
39962 readers
463 users here now
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.
Rules:
-
Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
-
No spam posting.
-
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
-
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
-
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
-
No trolling.
Resources:
- selfh.st Newsletter and index of selfhosted software and apps
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
On my machine it's consuming about 0.5% - 1.0% of cpu time, which is higher than zerotier in the same machine (almost zero).
Tailscale does a lot more things than just tunneling though. For example, on default installation it'll catch all outbound dns request on the machine and route them through MagicDNS (100.100.100.100).
That's weird. I closed the docker on that specific machine (ryzen 5), copied the docker-compose directory (=same config) on an i5-6500T and now it's using just 0.1% of CPU time.
Go back to ryzen and it's 8% again 🤷
I just checked my AMD box and tailscale there can consume ~15% of cpu time when the tunnel is under active use. When it's not used it's ~1.5%. But it's a low power old AMD cpu though (AMD G-T56N), so I'm not use if it compares to Ryzen 5. On my intel machine, it's ~5% when under active use, and idle at ~0.5%.
One thing you could try doing if you feel up to it is to build Tailscale from source code. Often when built for your specific machine, performance improves.
I use tailscale on my Ruzen system, and it always stays under 1% usage. Usually below 0.5%.
Isn't CPU % is per thread?