I’d nominate Bjork: All is Full of Love.
I’d nominate Bjork: All is Full of Love.
Hmm I think you just invented Marmite Butter, this needs to be a thing.
Ok, but messenger processes still operate in your PHP-fpm limits. The message queue only processes within those limits too, so you need to look at your fpm processes, see what the CPU / memory usage per process is like and then set the max accordingly.
You’re better off using htop to look at the actual processes running.
PHP-fpm had a memory per process setting and a few settings to control how many new processes can be spawned. You need to tweak this so that the CPU doesn’t hot 100%, I normally aim for a max of 90% but an average of around 50.
It it written using Symfony which is an extremely solid enterprise framework modeled on Java Spring.
PHP powers the majority of the web still and also has one of the largest development communities, proof of this usefulness is how many contributions have been made in the last few days: https://codeberg.org/Kbin/kbin-core/pulls
In the long run it will probably be a great advantage to Kbin to be written in PHP and for anyone who hasn’t seen the latest versions of PHP go look at the source code and have a look at all the recent improvements to the language.
It makes sense to do it that way otherwise everyone would see an empty page when they first signed up.
At least this way you can use the home page for discovery initially and once that gets too noisy use /sub as your homepage.
If you click through to some of the ones that indicate still public you can see they have gone into read-only mode rather than completely private.
From The Guardian’s article on this: