what is better for single user instance, or maybe something small like under 10 users (no communities)? which is lighter on resources? how much storage should I allocate?

any alternatives to lemmy and kbin that are still somewhat similar?

22 points
*

While I quite enjoy the Interface of KBin over Lemmy. It seems Lemmy uses a lot less resources based on the “Admin Guides” for each service.

Lemmy: https://join-lemmy.org/docs/en/administration/administration.html

KBin: https://codeberg.org/Kbin/kbin-core/wiki#user-content-admin-guide

permalink
report
reply
15 points

My Lemmy instance is currently occupying about 350MB of RAM, but you can round that up to 400MB. A lot less than the 4GB for KBin.Technically it’s a dual user instance now, since a friend wanted to join it and I said sure.

permalink
report
parent
reply
5 points

Damn, this is so much worse than good ol’ RSS for just following up stuff (which I imagine is the main argument to be made for a single-usee instance)

permalink
report
parent
reply
15 points

The arguments for are varied. I don’t have to worry about any admins making decisions on federation, I can federate (or not) however I please. I have my own space that I can do what I want with in a familiar format, and I can make my username Jamie without it being taken.

permalink
report
parent
reply
1 point

yeah for real I have been thinking the same lol. sadly a feed reader is just a reader. Would not be able to comment or post, which is the main reason I will go with a self hosted instance.

permalink
report
parent
reply
1 point

Keep in mind as php-fpm (used by Kbin) launches multiple child processes instead of a single rust process like Lemmy. The number of child processes can be tuned down to reduce RAM usage if necessary.

permalink
report
parent
reply
0 points

Thanks for the info! what about storage capacity usage?

permalink
report
parent
reply
8 points

After almost 24 hours, coming up on 662MB of images, and 371MB for the postegres database. Though, I could see the numbers fluctuating depending on how much stuff you’re subscribed to. I’m currently subscribed to 31 communities, most of them fairly large.

permalink
report
parent
reply
3 points

BeeHaw.org admin said like a week ago they were only up to 25GB.

permalink
report
parent
reply
5 points

Yeah, kbin seems to be a php8 service vs a compiled rust service from some lite poking.

permalink
report
parent
reply
16 points

I was also looking into both but in the end I chose lemmy because I didn’t want to deal with PHP.

permalink
report
reply
13 points

Lemmy should be lighter on resources, since it’s written in Rust.

permalink
report
reply
6 points

Far, far lighter on RAM for sure. Less than half a gig for Lemmy, multiple gigs for KBin

permalink
report
parent
reply
1 point

Kbin is PHP app so you should be able to tune down idle worker counts to use less memory. Certainly not as low as Lemmy being a compiled rust app, but 500 MB of RAM usage should be achievable. As for CPU usage, I’ve been running a personal Lemmy instance and I’m impressed with how low the CPU usage so far, even after federating with dozens communities. Can’t say the same about Kbin because I haven’t actually run it myself, but PHP 8’s JIT is very fast so I imagine it shouldn’t use too much CPU as well.

permalink
report
parent
reply
7 points

@cyclohexane I think this should be merged today with a bit of luck: https://codeberg.org/Kbin/kbin-core/pulls/143

permalink
report
reply
2 points

That’s great, glad to see progress on simplifying deployment!

permalink
report
parent
reply
0 points

Really glad to see this, will make deployment much easier.

permalink
report
parent
reply
6 points

I’m definitely interested in seeing how the single-user instance offerings develop across the various federated applications. I have no interest in taking on the role of admin or moderator for people I don’t know personally, but am more than happy to run my own front-end service that’ll let me lurk and interact with all varieties of ActivityPub content.

For now it seems kbin might win that fight for me since it’s equipped to handle reddit-style communities and threads while also providing a workable microblog interface. But it does seem to be a bit on the heavy side… I wonder if we might see some software created for this particular usage scenario one day, if it isn’t already being worked on somewhere.

permalink
report
reply
6 points

If big instances like Beehaw go whitelist federation only, it will effectively make single user instances useless.

permalink
report
parent
reply
5 points

Certainly a possibility, but I don’t really expect it to be a common concern. Defederation is mostly about keeping problematic people out when an instance’s admins either can’t or won’t resolve whatever problem is at play. Most instances will never even realize a single-user instance is lurking at all if they don’t bother to crawl the logs and said user doesn’t cause a scene.

I’d expect most whitelist-only instances will have been that way from the start instead of growing large and then shutting the door, because the goals of running an instance like that are fundamentally different.

permalink
report
parent
reply
1 point

Yeah, I think a whitelist only instance would to dramatically limit its users to be generally attractive for most people, and would certainly keep it from becoming popular. They are surely use cases for it but pretty limited I’d imagine.

permalink
report
parent
reply
3 points

Right now they went the other way around, so the big instances are blocked and we with our single user ones can still federate with them.

permalink
report
parent
reply
1 point

The barrier to entry for making a new instance is relatively high compared to the barrier for entry for making an account on a free for all instance, so I doubt it will be an issue.

permalink
report
parent
reply

Selfhosted

!selfhosted@lemmy.world

Create post

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!

Community stats

  • 4.9K

    Monthly active users

  • 3.6K

    Posts

  • 81K

    Comments