this post was submitted on 11 Oct 2023
60 points (98.4% liked)

Selfhosted

40023 readers
1245 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:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

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

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

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

Questions? DM the mods!

founded 1 year ago
MODERATORS
60
Cost-cutting tips? (discuss.tchncs.de)
submitted 1 year ago* (last edited 1 year ago) by nutbutter@discuss.tchncs.de to c/selfhosted@lemmy.world
 

What are your favourite, or least favourite but necessary, cost-cutting methods?

I feel I am spending too many resources on unnecessary stuff.

Edit: I feel the need to reduce both – the resources, to host multiple things on one system, and cost, to buy/pay for multiple systems. Currently, I have 2 ARM VPSes and 1 old MacBook Air as a home server.

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

I see the question has been understood in two ways: cost in computer resources and money. Which one did you mean?

[–] Anafroj@sh.itjust.works 6 points 1 year ago* (last edited 1 year ago)

That's the same thing. :) If you reduce computing load, you reduce the need for costly hardware and you reduce the need for energy, thus you reduce the amount of money needed to build and run your setup. There's a saying in (software) engineering : "reducing energy consumption and increasing performances requires the same optimizations". Make your code faster (by itself, not by buffing up hardware) and it consumes less energy. Make your application simpler, and it will run faster, and it will consume less energy. It's not an absolute truth (it sometimes happen that you make your code faster and it consumes more energy), but it's true most of the time.