Selfhosted

63371 readers

677 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:

Detailed Rules Post

Be civil.
No spam.
Posts are to be related to self-hosting.
Don't duplicate the full text of your blog or readme if you're providing a link.
Submission headline should match the article title.
No trolling.
Promotion posts require active participation, with an account that is at least 30 days old. F/LOSS without a paywall has exceptions, with requirements. See the rules link for details. Tags [CBH] or [AIP] are required, see the links in Rule 8 for details.
AI-related discussions and AI-involved promotional posts have additional requirements for tagging, as noted in Rule 7 and the AI & Promotional Post Expanded Rules post, and find example disclosures here.

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 3 years ago

MODERATORS

curbstickle@anarchist.nexus

curbstickle_lw@lemmy.world

Beszel vs Netdata vs Glances: only Netdata publishes a RAM footprint, and its README and docs give different numbers (lemmy.world)

submitted 2 hours ago by iBlessi@lemmy.world to c/selfhosted@lemmy.world

4 comments fedilink hide all child comments

Footprint numbers on other comparison pages had no reproducible method, so I read the releases and docs for all three on September 26, 2026 (Beszel v0.20.0, Netdata v2.11.1, Glances v4.5.7).

Only Netdata publishes one. Beszel's README says it's less resource-intensive than leading solutions and stops there. Glances says nothing. Netdata's resource-utilization page says 100-200 MB of RAM on an empty system and 250-350 MB in typical production, while its README says about 150 MiB and 5% CPU on production systems. Two pages, two answers.

History with nothing added differs a lot. Beszel keeps 1-minute points for an hour and averages up to 30 days. Netdata keeps per-second data up to 14 days, per-minute up to 3 months and per-hour up to 2 years, about 4 GiB of disk. Glances holds 1,200 values per stat in memory, about an hour.

Gotchas. Beszel v0.19.0 made agents verify the hub's HTTPS certificate, so a self-signed hub now needs CA_CERT_FILE. Issue #176 reports Beszel agents inside LXC showing the host's RAM. Netdata Cloud dashboards give access to 5 nodes without a paid plan (streaming to a Parent isn't capped), and Homelab was $90 a year when I read it.

I'd run a Beszel agent on every host and Uptime Kuma outside the network, with Netdata only on the box I'm debugging.

Every footprint figure here is the project's own claim, not my measurement. The page has a pidstat recipe for measuring your own: https://techfuelhq.com/homelab/beszel-vs-netdata-vs-glances-2026/

you are viewing a single comment's thread
view the rest of the comments

[–] solrize@lemmy.ml 6 points 1 hour ago (2 children)

Um what are these things and who should care? That info would help a post like this.

"Beszel" is Hungarian for "speak" if anyone cares.

[–] observantTrapezium@lemmy.ca 0 points 9 minutes ago

I came here to say exactly these two things 😂

[–] IsoKiero@sopuli.xyz 1 points 1 hour ago

Um what are these things and who should care? That info would help a post like this.

Absolutely. For anyone else wondering: they are some kind of monitoring tools for your servers. No idea how good/useful they are, I've never head any of those before.