this post was submitted on 12 Dec 2025
15 points (89.5% liked)

Selfhosted

61451 readers
610 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

  1. Be civil.

  2. No spam.

  3. Posts are to be related to self-hosting.

  4. Don't duplicate the full text of your blog or readme if you're providing a link.

  5. Submission headline should match the article title.

  6. No trolling.

  7. 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.

  8. 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:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 3 years ago
MODERATORS
 

Folks,

I have an Intel N5095 2 GHz box, with 16 GB RAM and 500 GB sitting below my desk. It's a teeny tiny box with no fan or anything.

I'm currently running Debian server on it with Portainer on top to run some *arr services. I'm thinking of running some more. But the device seems to groan under the weight of the services already running.

Was just watching a video about proxmox, and it seems to be a better solution if I don't need to run Portainer on top of an OS. Maybe it'll be lower resource usage?

So, thoughts? Should I change it up from Debian to proxmox? Or should I stick to what is already running? I am running Debian because I read somewhere that it's the lowest resource hog of all Linux server options.

Alternatively, should I stick to Debian and portainer but use it with something like podman as it might use less resources than docker-ce?

you are viewing a single comment's thread
view the rest of the comments
[–] damnthefilibuster@lemmy.world 1 points 8 months ago (1 children)

temp

I installed a thing called lm-sensors on debian and it shows me this during a time when the box is struggling -

Every 1.0s: sensors

coretemp-isa-0000 Adapter: ISA adapter Package id 0: +44.0°C (high = +105.0°C, crit = +105.0°C) Core 0: +38.0°C (high = +105.0°C, crit = +105.0°C) Core 1: +39.0°C (high = +105.0°C, crit = +105.0°C) Core 2: +39.0°C (high = +105.0°C, crit = +105.0°C) Core 3: +39.0°C (high = +105.0°C, crit = +105.0°C)

acpitz-acpi-0 Adapter: ACPI interface temp1: +0.0°C (crit = +119.0°C)

Seems to be working fine.

Unless the thermal throttling limits are set by the BIOS and I'll have to go looking into that by rebooting?

Resources also seemed ok - RAM was 2 GB used out of 16 and all the cores were at 10-15% usage, according to htop.

[–] wreckedcarzz@lemmy.world 2 points 8 months ago (1 children)

Yeah, that all looks okay. Did you put the system under heavy load while checking/monitoring?

[–] damnthefilibuster@lemmy.world 1 points 8 months ago (1 children)

I was just trying to open my transmission dashboard! 😄

[–] wreckedcarzz@lemmy.world 2 points 8 months ago

Have the system do something intensive and see how much the temps climb. Let it work for a few minutes and see - that will tell you if your system is thermal throttling or not.