this post was submitted on 27 Nov 2023
10 points (100.0% liked)
Self-Hosted Main
515 readers
1 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.
For Example
- Service: Dropbox - Alternative: Nextcloud
- Service: Google Reader - Alternative: Tiny Tiny RSS
- Service: Blogger - Alternative: WordPress
We welcome posts that include suggestions for good self-hosted alternatives to popular online services, how they are better, or how they give back control of your data. Also include hints and tips for less technical readers.
Useful Lists
- Awesome-Selfhosted List of Software
- Awesome-Sysadmin List of Software
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
What is wrong with RPi? I thought RPi 4 for two calendars (one calendar per user) on nextcloud would be plenty, looking at the requirements:
Also, how resource intensive could/should be syncing two personal calendars (via Thunderbird)? I don't understand, why NextCloud with this virtually negligible task struggles so much. The pi has 7+GB of free memory, CPU load under few %, rarely one core has some load, most of the time nothing accesses the card nor disk (virtually 0 iowait; only with a short spike once every 5 minutes). Why does Nextcloud take half a minute to several minutes for a sync of one calendar in Thunderbird?
Its underpowered, especially for an application based on PHP which is single threaded so requires a core with a fast clock. The RPi4 with 1.5Ghz is woefully underpowered to drive anything php backed.
I see 1.8GHz in glances (in my case actively cooled, but since it doesn't seem to max any core, it probably doesn't matter). I have other RPi4s, I wonder why is backend in Java (well, Scala) ok, backend in Haskell ok, but backend in PHP wouldn't be? I still don't understand how Nextcloud can lock up for so long (tens of seconds) on a simple write event into calendar operation. That hacky unoptimized Java BE which does joins manually and inserts sequentially (so from a db perspective just awful), handles 5-10 times more data and still does it order of magnitude faster. My old phone which was weaker than even RPi4 could handle dozens of such small operations in one second (I believe that was SQLite + Java). There must something seriously wrong with Nextcloud (including PHP runtime) and/or the RPi, because such insignificant amount of data (1 word title, one date, one reminder option), most likely merely few dozens of bytes, takes so incredibly long to process and write to db...
i cant comment on the differences between languages, but it probably also has a lot to do on how nextcloud is written. unoptimized software is always going to be slower than it's counterpart.