Skip to main content


The Hubzilla database is filling up...


The Hubzilla database is filling up with content, slowly but steady...

77a701bc74ba66773dd6780385997e55e06709df80045bd590ff3c70645f287f-1.png

It will need some more days and more contacts to match the size of my #Friendica database. ;)
in reply to Ingo Jürgensmann

Hmm, can't comment on that. Sure, for a single user hub (at the moment I'm the only user), this seems quite a lot, but I'm curious how this evolves when more users have registered and are using this hub. We'll see... 😀
in reply to Ingo Jürgensmann

It's complete open. At least when I understood the configuration correctly... 😎 (if not, please tell me!)
in reply to Ingo Juergensmann

I was just curious, I have enough to do with understanding Friendica myself. 😀
in reply to Ingo Jürgensmann

It will be rather big hub.
I'm running diaspora pod os about 1800 users (around 1000 active in last 6 months) for last three years and the db is 5.5GB
On the other hand I run one of the largest matrix servers with few k users and rooms for a year and half and thats 356GB
in reply to Ingo Jürgensmann

@foosahunter: I guess the database can quickly grow, ever increasing, when you don't purge old content. There are settings in #Friendica to delete old remote content (own content will not be purged) and you can have something similar in Hubzilla as well, I guess.

Although there is much disk space left on the server (currently >1 TB), I don't indent to let it grow that big. Maybe a database size of approx. 50 GB would be ok, but that really depends on the database performance how large I let the DB grow. IMHO #PostgreSQL is better for large databases than #MySQL/#MariaDB, for which the recommendation is often to make the buffers so large that the database fits into RAM. I used mysqltuner to adjust the settings accordingly:

[--] Physical Memory : 31.3G<br></br>[--] Max MySQL memory : 12.7G<br></br>[--] Other process memory: 4.1G<br></br>[--] Total buffers: 12.2G global + 3.1M per thread (151 max threads)<br></br>[OK] Maximum reached memory usage: 12.3G (39.34% of installed RAM)<br></br>[OK] Maximum possible memory usage: 12.7G (40.51% of installed RAM)<br></br>[OK] InnoDB buffer pool / data size: 12.0G/7.2G
Well, I did the tuning before upgrading to #Friendica 3.6 which did some database changes and freed up some database space. It was 11 or 12 GB back then.

Contrary the #PostgreSQL settings:

work_mem = 20971kB <br></br>maintenance_work_mem = 1GB <br></br>
In top this shows like this:
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND<br></br>26186 mysql 20 0 14.868g 0.011t 12204 S 1.7 35.4 673:51.64 mysqld<br></br> 4215 postgres 20 0 4459276 3.120g 3.117g S 0.0 10.0 17:58.64 postgres<br></br> 4216 postgres 20 0 4458300 282988 281248 S 0.0 0.9 0:51.59 postgres<br></br> 4209 postgres 20 0 4458408 119684 117764 S 0.3 0.4 147:24.34 postgres
So, both DBMS are running on the same server (32 GB RAM, RAID10). There is some physical RAM left over, so I could add another bunch of 32 GB to that host and would still have 20 GB RAM for other VMs, e.g. the webserver VM (currently 16GB).

Long story short: I don't fear a bunch of more users. 😉
in reply to Ingo Jürgensmann

Ahhh... so there is a way to purge content from the database? That sounds already promising as keeping the entire fediverse forever seems like a huge storage challenge.

You mentioned friendica, I wonder if there are tools/scripts to purge old remote content form the server.
in reply to Ingo Jürgensmann

There are some config settings. In current stable version 3.6 you'll need to apply those settings in .htconfig.php, in current dev branch I think there's some GUI setting for this:

// for database cleanup:<br></br>$a->config['system']['dbclean'] = true;<br></br>$a->config['system']['dbclean-expire-days'] = 365;

For #Friendica you maybe can ask @alfred@libranet.de (@alfred@hub.libranet.de) about the database size