Everything is faster. For the most part, your local instance will download posts and comments for any community you (or anyone else on your instance) is subscribed to. So when you log in, you log into your server and browse the content locally (posts from everywhere) while your server in the background constantly is receiving updates through the ActivityPub protocol.
I literally have no delay in using Lemmy in any way.
The “all” stream would be all of the posts from the combined subs of the users on the instance. So if there’s a community nobody is subscribed to, it won’t appear on all. This is true of all instances. Many smaller ones will employ bots to crawl Lemmy and sub to communities to give the large instance “all” feeling.
That being said, yeah it’s all preloaded onto your local server. There is no difference in speed. Doesn’t matter if it’s active/subed or new/all they all load the same
I’d highly encourage everyone to find smaller instances and leave lemmy.world for the immediate expats. Find something that aligns with your values. Or if you are technically literate enough host your own instance. If you have an old desktop computer you’ve already got everything you need.
In just a week, With BTRFS compression (compress-force=zstd:3) & deduplication (via bees), media is at about 1GB (and I am subscribed to media-heavy communities like 196) and the postgres DB is at about 550MB (which is also currently shared with Matrix Dendrite)
At “idle” (as you can be while being connected to ActivityPub & Matrix), the immediate CPU and RAM usage breakdown per container is:
Net IO you shouldn’t really care about as that includes inter-container networking. I’m trying to find how much outgoing data have been transferred but because the month just ended I have no idea how accurate the numbers are.
On my instance we’ve got about 100 communities subscribed to. Started it first week of June, since then the instance is up to a little over 4 GB of disk space. YMMV depending on instance size.
On my instance we’ve got about 100 communities subscribed to. Started it first week of June, since then the instance is up to a little over 4 GB of disk space. YMMV depending on instance size.
On my instance we’ve got about 100 communities subscribed to. Started it first week of June, since then the instance is up to a little over 4 GB of disk space. YMMV depending on instance size.
Everything is faster. For the most part, your local instance will download posts and comments for any community you (or anyone else on your instance) is subscribed to. So when you log in, you log into your server and browse the content locally (posts from everywhere) while your server in the background constantly is receiving updates through the ActivityPub protocol.
I literally have no delay in using Lemmy in any way.
What about the “all” stream? Is that also preloaded to the server?
The “all” stream would be all of the posts from the combined subs of the users on the instance. So if there’s a community nobody is subscribed to, it won’t appear on all. This is true of all instances. Many smaller ones will employ bots to crawl Lemmy and sub to communities to give the large instance “all” feeling.
That being said, yeah it’s all preloaded onto your local server. There is no difference in speed. Doesn’t matter if it’s active/subed or new/all they all load the same
I’d highly encourage everyone to find smaller instances and leave lemmy.world for the immediate expats. Find something that aligns with your values. Or if you are technically literate enough host your own instance. If you have an old desktop computer you’ve already got everything you need.
I should probably build an instance on my little home server. Is there a guide for that somewhere?
Right on the lemmy website. 🙂
https://join-lemmy.org/docs/administration/administration.html
It can apparently take up a decent amount of space depending on how many communities you subscribe to.
https://github.com/LemmyNet/lemmy-ansible
There you go, enjoy
How many communities you subscribed and after two weeks how much data does it represents on your storage ?
Not OP but I can answer with my own stats:
In just a week, With BTRFS compression (compress-force=zstd:3) & deduplication (via bees), media is at about 1GB (and I am subscribed to media-heavy communities like 196) and the postgres DB is at about 550MB (which is also currently shared with Matrix Dendrite)
At “idle” (as you can be while being connected to ActivityPub & Matrix), the immediate CPU and RAM usage breakdown per container is:
NAME CPU % MEM USAGE / LIMIT MEM % NET IO BLOCK IO PIDS CPU TIME AVG CPU % pict-rs 0.20% 18.92MB / 4.005GB 0.47% 3.319GB / 1.105GB 17.58GB / 3.239GB 13 1h16m57.232828s 0.59% crowdsec 1.39% 44.23MB / 4.005GB 1.10% 106.4MB / 23.46MB 25.53GB / 486.7MB 11 45m28.744419s 1.95% caddy 0.63% 73.06MB / 4.005GB 1.82% 1.675GB / 1.977GB 3.322GB / 720MB 10 21m9.94572s 0.90% dendrite 1.58% 197.7MB / 4.005GB 4.94% 912.8MB / 2.33GB 8.718GB / 4.761GB 12 53m26.302022s 1.43% postgres 5.33% 82.51MB / 4.005GB 2.06% 56.22GB / 7.961GB 20.92GB / 295.7GB 23 8h20m28.078567s 2.86% lemmy-ui 0.00% 48.71MB / 4.005GB 1.22% 3.491GB / 5.961GB 3.603GB / 5.267GB 12 31m35.884936s 0.24% lemmy-be 2.82% 29.01MB / 4.005GB 0.72% 16.45GB / 57.85GB 7.966GB / 6.439GB 6 3h6m34.633508s 1.42%Net IO you shouldn’t really care about as that includes inter-container networking. I’m trying to find how much outgoing data have been transferred but because the month just ended I have no idea how accurate the numbers are.
On my instance we’ve got about 100 communities subscribed to. Started it first week of June, since then the instance is up to a little over 4 GB of disk space. YMMV depending on instance size.
On my instance we’ve got about 100 communities subscribed to. Started it first week of June, since then the instance is up to a little over 4 GB of disk space. YMMV depending on instance size.
On my instance we’ve got about 100 communities subscribed to. Started it first week of June, since then the instance is up to a little over 4 GB of disk space. YMMV depending on instance size.
I do that on my own instance too :D, private and small instances are really the way to go!