bolha.us is one of the many independent Mastodon servers you can use to participate in the fediverse.
We're a Brazilian IT Community. We love IT/DevOps/Cloud, but we also love to talk about life, the universe, and more. | Nós somos uma comunidade de TI Brasileira, gostamos de Dev/DevOps/Cloud e mais!

Server stats:

252
active users

#mariadb

3 posts3 participants0 posts today

For our May meetup (that's the one after the next one) we have @mariadb_org as a host and they are also organising a hackathon! There are a few €500 Verkkokauppa gift cards as prizes for the best use of their new vector extension to @mariadb.

Deadline for sign up is Monday (31st). Find out more details via their announcement blog post, and join up on our Discord via helsinki-python.github.io

Helsinki Python logo
helsinki-python.github.ioHelsinki PythonA local usergroup for the Greater Helsinki region meeting up roughly every month
Replied in thread

@keira_reckons

Most Relational DBMSen (#PostgreSQL, #MariaDB, etc.) have explicit options, when defining a foreign key relationship, to declare what must happen; see "ON DELETE RESTRICT", "ON UPDATE CASCADE", and the like.

#Django ORM `ForeignKey` currently allows specifying the "on delete" referential actions, but not "on update". code.djangoproject.com/ticket/

code.djangoproject.com#21295 (Add on_update support) – Django

As my #Friendica server, my-place.social, has grown to some 315 active users in just 5 months, I'm starting to hit up against #mariaDB limitations relating to the default memory manager, #MALLOC. This weekend I'm going to replace it with #jemalloc to reduce stalls, memory fragmentation issues, out-of-memory problems, and instability.

Friendica puts a lot of pressure on the database, mariaDB in this case, much more than Mastodon apparently does on PostgreSQL. My feeling is that the Mastodon developers have done much better database tuning.

But, none-the-less, the update must be done. This will be done on an Ubuntu server.

Does anyone who has changed the MariaDB or mySQL memory manager have any advice to share to keep me out of trouble?

BTW, #TCMalloc is not an option as other admins have reported crashes using it with Friendica.