Selfhosted

Fasting allows you to waste less money on food and invest more money into your server.

Cost-cutting is corporate-greed mindset, therefore you have to solve it with the same mindset.

Fire people ! Even you if needed. And let the end-users deal with the outcome.

(This is not a serious post ^^ )

My favorite cost cutting tip is to avoid big webapps running on docker, and instead do with small UNIX utilities (cron instead of a calendar, text files instead of note taking app, rsync instead of a filehosting dropbox-like app, simple static webserver for file sharing, etc). This allows me to run my server on a simple Raspberry Pi, with less than 500mb of used RAM in average, and mininal energy consumption. So, total cost of the setup:

• Raspberry Pi : 77€ x 2 = 144€ (I bought two to have a backup if the first one fails)
• MicroSD 64gb : 13€ x 2 = 26€ (main and backup)
• average energy consumption : 0.41€ (2kWh) per month

With that, I run all services I need on a single machine, and I have a backup plan for recovery of both hardware and software.

Getting used to a UNIX shell and to UNIX philosophy can take some time, but it's very rewarding in making everything more simple (thus more efficient).

• Use sqlite instead of Postgres, MariaDB
• Avoid enterprise software (Kubernetes, Elastic Search)
• Only use projects with efficient programming languages such as Go, Rust, etc.
• Try to run things bare metal
• Lookout for projects which name themself minimal or light-weight

I use a Raspberry Pi 2 to self host a Dashboard written in Rust (Axum), a RSS reader called yarr and a music streaming server Navidrome. The latter two are written in Go and very resource efficient. The electricity bill should be under a Euro a month (6.4W max power consumption).

You only need to eat two meals a day, really.

My least favourite (and only) method for me to cut costs is reduce my energy consumption.

I already have a super cheap setup (used Mini-PC for 50 bucks, old SSDs I had lying around, etc.), so reducing the hardware costs more isn't possible.

But, without tweaks, this setup would eat 15W (idle) and 25W (under load) electricity. At least, thats the case atm.

I just started selfhosting to be fair, and I didn't have time to throttle the server. I use it mainly as NAS, so speed isn't as important in this case as for other services like webapps, where reactivity is needed.

The CPU isn't too bad, so, even when reducing the performance to 50%, it should still work.

Also, I will try to change the active cooling fan to a passive heat sink, that might reduce the bill further.

What mainly eats resources like crazy is my Nextcloud AIO. I try to follow the UNIX-principle as good as I can, and NC doesn't follow it well, at least for my use case.

I only need a file server, and NC is pretty "bloated" with talk, calender, and so on. So I disabled all of that.

But, I'm not capable enough to set up an Online-FTP-Server and secure it enough without ever working in that environment. NC AIO provides a lot of comfort and "just works". So, I'm fine with that.

Here in Germany, especially thanks to the energy crisis, electricity is absurdly expensive, and even reducing the TDP by a few % will save me much money over a year.

So, I try to reduce the load and increase efficiency wherever I can.

Still, even now, with an increased energy consumption + paid domain, it's still cheaper than using OneDrive or something like that, even when ignoring storage size.

Running stuff on my bare metal servers is my go to cost saving measure. Why rent 2 VPSes if you can buy some old thin clients and turn them into linux servers, etc.

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

Make a spreadsheet of where your money is going.

https://paul.totterman.name/posts/free-clouds/

Or then you can just realize that the time you spend is spent not making money and you need to save time, not services.

Acronyms, initialisms, abbreviations, contractions, and other phrases which expand to something larger, that I've seen in this thread:

7 acronyms in this thread; the most compressed thread commented on today has 9 acronyms.

[Thread #208 for this sub, first seen 11th Oct 2023, 08:45] [FAQ] [Full list] [Contact] [Source code]

Im quite new in selfhosting, but I highly recommend power meter for home server if you dont have one. Its easy to tell the difference after any change in your setup. I was surprised with numbers when I was testing different PSUs on DIY PC. All PSUs were overkill (550-750W) for my tiny server (they are not made for that low power), but some cheap models were better than more expensive PSU. I was meassuring from 22-28 W iirc on idle. Its only 6W difference, but thats like 25%. I dont use VPS because I have no need for that and even cheap ones are more expensive than running my home server. Some servers can run at <10W and raspberry pi use even less power

Run less stuff.

It is a little dangerous to do in case you experience a crash or a power failure, but you can get a lot more bang for the buck from your server hardware if you have a decent amount of memory by tuning your different system components to keep more data in memory and write to disk less often. This can be done with sysctl.conf and dirty writes, or with php or MySQL using more working memory and not writing to disk as often.

It was particularly required when I was still using a spinning drive, since random io was a show stopper. Even using a decent sata SSD it can be beneficial however, letting the system choose to write at more opportune moments instead of doing it in the middle of read ops.