What is the correct setup

xasharma

Hey guys, please tell me what to use and how to use them

I am currently using only FriendsOfFlarum Redis sessions, cache & queues

So please tell me, can I use Database Queue ?

And can I use Flarum scheduler with the FriendsOfFlarum Redis sessions, cache & queues ?

So please tell me what I can use with FriendsOfFlarum Redis sessions, cache & queues and in what order to use. And Do they help in increasing the speed of the Flarum site ?

FBI

For me, Normal Flarum speed was okay, without that complex required.
Maybe We have different view what is speed? DNS? Query? Client Load? Hosting? etc..
Do you have huge big forum with millions of posts? 🙂

https://discuss.flarum.org/d/37313-speed-of-flarum

xasharma

FBI We have around 200k Posts and 25k discussions

Please someone guide about these extensions and their work on the forums

luceos

The scheduler is used to fire repetitive tasks like reminders. And it also triggers the database queue if you use that. The scheduler (cronjobs) by itself don't improve performance, though the database queue does. I wrote why a queue helps in the extension page for database queues:

luceos By default, Flarum runs without a (background) queue. This means that all tasks of Flarum are processed during the request of the user.

A great example of this is email sending. When using flarum/subscriptions, fof/follow-tags, ianm/follow-users or any other extension that allows subscribing to things, email sent out to notify users. For smaller communities this is not a big deal, but at some point you'll notice your requests (posting for instance) may start to slow down. All of these emails are dispatched after the post is stored to the database.

To resolve this increasing burden, you can run a Queue. A queue runs on your server, it does not interact with the user and their requests. A user request, however, can dispatch tasks to the queue. This extension provides the easiest implementation of a queue and works on shared hosting environments as well.

The database queue is the simplest implementation of a queue. It doesn't run background tasks instantiously, but with a max delay of one minute. The redis queue is immediate and if you use the horizon extension scales very well. All redis based queues do need a daemon that runs on your server, and as such usually isn't a viable option on shared hosting environments.

The other areas that the redis package adds are cache and sessions. For simple, small communities you won't necessarily need these. Redis cache and sessions are great primarily on horizontally scaled hosting environments, where you use multiple servers to run your community.

xasharma

luceos Thank you for the explaning this so great.

My last question is - Please tell me what i use with FriendsOfFlarum Redis sessions, cache & queues to speed up more for a larger community ?

xasharma

clarkwinkelmann Thank you for brief help.

clarkwinkelmann

luceos

You are correct, I don't know much about the extension, My last question is - Please tell me what i use with FriendsOfFlarum Redis sessions, cache & queues to speed up more for a larger community ?

What i should use for larger forums - Database Queue or Flarum scheduler or both or none ?

xasharma

xasharma My last question is - Please tell me what i use with FriendsOfFlarum Redis sessions, cache & queues to speed up more for a larger community ?

Anyone please help to understand this.

@luceos @clarkwinkelmann and team

clarkwinkelmann

Here are my suggestions:

If you don't know/understand what the extension can do, don't install it.

If you want to experiment with those more advanced features, create a test forum with the same server hardware, populate it with either a copy of your production database (make sure to disable all outbound email!) or fake test data, then run tests with each combination of settings you're interested in.

Luceos described why you might want to use one feature or the other pretty well above.

The extensions themselves are very easy to configure, as far as I know all you need is to fill in the redis server config and choose which features to enable. If you encounter errors or something doesn't work as expected, please share the steps you took and describe what happens.

clarkwinkelmann

xasharma if you have the resources (both hardware, and ability to monitor), using an asynchronous queue is always better. Using the redis queue instead of the database queue will be slightly more efficient, but in the end it depends what is easier to deploy and maintain on your hosting.

The scheduler is a requirement for some extensions. If you don't use any extension that relies on the scheduler, you can configure it in advance, but it won't do anything. The extension README file will let you know if you need it. Some extensions only need it for certain configurations (example: FoF Sitemap can work with or without it depending on the execution mode). Some extensions can work with either the scheduler or its own entry in the CRON configuration, for those extensions if you choose CRON you might not need the scheduler unless other extensions require it.

The 2 features are completely unrelated. You can configure both if you need both.