These are current graphs for lemmy.world (yet to add it to my Zabbix)
Diskspace:
du -sm *
960 pictrs
1273 postgres
I see you're using Hetzner.
Those graphs don't really show what kind of CPU you're using. It's a 2 core i guess?
It was an 8 core. But the current server is a 32-core / 64 thread cpu.
For only 17k Users? Seems like a lot of CPU Usage. Damn.
it's most likely coming from postgres, db server tends to be the main resource hog.
I think it depends heavily on how much storage you're allocating, if you allow uploading media that is. From what I've understood most of the bottlenecks are in DB operations so CPU and memory definately play a role.
Good point. I forgot about media.
I wonder if I made a LAN lemmy instance if I could use it as a lemmy cache server.
Is there a such thing as a cache only server? If so I'd love to sign up as being a cache bitch and help out!
I've not looked to see if it's possible, but a lemmy instance with posting disabled would be effectively be a cache server - all reads, no writes, except for sign ups, I think.
At least 2.8k :-)
What is the plan to make communities between instances easily accessible? I feel like with mastodon and now lemmy that is the part that concerns me, namely community reach/discoverability
External communities are just searchable, subscribable and browsable from here. Sometimes you need to change a search filter or default view from Local to All.
Or is there something else you feel is missing?
I think 90% of the issues people are having are UX related and not a core issue with federation or decentralization.
I think my concern for adoptability is that a technology community could exist with the same name on lemmy.world as well as on another instance. I think theirs some benefit to creating a user and community pool of names and communities to allow genuine growth. it would also prevent fakes and phishing.
I think of it like selfhosted@lemmy.world instead of just selfhosted. Sure there may be duplicate communities on different instances but over time I think there will be more people gravitating to a particular community and people will just sub there from then on and the others will become more dormant. When I refer to a community I'll just use the full name (selfhosted@lemmy.world) and not just the community name (selfhosted)
These are current graphs for lemmy.world (yet to add it to my Zabbix)
Diskspace:
I see you're using Hetzner. Those graphs don't really show what kind of CPU you're using. It's a 2 core i guess?
It was an 8 core. But the current server is a 32-core / 64 thread cpu.
For only 17k Users? Seems like a lot of CPU Usage. Damn.
it's most likely coming from postgres, db server tends to be the main resource hog.
I think it depends heavily on how much storage you're allocating, if you allow uploading media that is. From what I've understood most of the bottlenecks are in DB operations so CPU and memory definately play a role.
Good point. I forgot about media.
I wonder if I made a LAN lemmy instance if I could use it as a lemmy cache server.
Is there a such thing as a cache only server? If so I'd love to sign up as being a cache bitch and help out!
I've not looked to see if it's possible, but a lemmy instance with posting disabled would be effectively be a cache server - all reads, no writes, except for sign ups, I think.
At least 2.8k :-)
What is the plan to make communities between instances easily accessible? I feel like with mastodon and now lemmy that is the part that concerns me, namely community reach/discoverability
External communities are just searchable, subscribable and browsable from here. Sometimes you need to change a search filter or default view from Local to All. Or is there something else you feel is missing? I think 90% of the issues people are having are UX related and not a core issue with federation or decentralization.
I think my concern for adoptability is that a technology community could exist with the same name on lemmy.world as well as on another instance. I think theirs some benefit to creating a user and community pool of names and communities to allow genuine growth. it would also prevent fakes and phishing.
I think of it like selfhosted@lemmy.world instead of just selfhosted. Sure there may be duplicate communities on different instances but over time I think there will be more people gravitating to a particular community and people will just sub there from then on and the others will become more dormant. When I refer to a community I'll just use the full name (selfhosted@lemmy.world) and not just the community name (selfhosted)