ReCache - Speed up your forum

[deleted]

@Kyrne I can't seem to use @askvortsov Categories extension anymore 😢

Your requirements could not be resolved to an installable set of packages.

  Problem 1
    - askvortsov/flarum-categories v0.2.6 conflicts with reflar/recache[2.0.3].
    - askvortsov/flarum-categories v0.2.6 conflicts with reflar/recache[2.0.3].
    - askvortsov/flarum-categories v0.2.6 conflicts with reflar/recache[2.0.3].
    - Installation request for askvortsov/flarum-categories ^0.2.6 -> satisfiable by askvortsov/flarum-categories[v0.2.6].
    - Installation request for reflar/recache (locked at 2.0.3, required as ^2.0) -> satisfiable by reflar/recache[2.0.3].


Installation failed, reverting ./composer.json to its original content.

Kyrne

[deleted] how'd that fossil of code get in there? 🐶 Try again now.

[deleted]

Kyrne All sorted. Thanks

[deleted]

@Kyrne I think ReCache needs some flashy stats around caching - for example, assets cached, DB queries cached etc....

Kyrne

[deleted] sounds like something that might slow it down haha.

I'll look into it.

[deleted]

Kyrne sounds like something that might slow it down haha.

I meant in the dashboard 🙂

mekici

Hello @Kyrne. Thank you for the quick updates. However, it seems that I have a new problem. Sitemap.xml page gives 500 error when activating the plugin.

recache version: 2.0.4

[deleted]

mekici for me, sitemap.xml throws a 404

mekici

[deleted] There is an apparent problem.

[deleted]

mekici now a http 500 if I disable and enable the extension

mekici

[deleted] When I disable the plugin, the site gives a complete 500 error.

Kyrne

2.0.5

No longer caches direct file links and auth (sitemap, SSO, etc)

run: php flarum cache:clear and the issue will be fixed.

mekici

A 500 error will be thrown when you disable if the Redis server is turned off before the extension is disabled. This is a conscious decision and was put in place intentionally.

DursunCan

No log record occurred.

Notice: Undefined offset: 0 in /var/www/sourceturk/forum/vendor/reflar/recache/src/Replacers/Data.php on line 66

Fatal error: Uncaught Laminas\HttpHandlerRunner\Exception\EmitterException: Output has been emitted previously; cannot emit response in /var/www/sourceturk/forum/vendor/laminas/laminas-httphandlerrunner/src/Exception/EmitterException.php:24
Stack trace: #0 /var/www/sourceturk/forum/vendor/laminas/laminas-httphandlerrunner/src/Emitter/SapiEmitterTrait.php(40): Laminas\HttpHandlerRunner\Exception\EmitterException::forOutputSent() #1 /var/www/sourceturk/forum/vendor/laminas/laminas-httphandlerrunner/src/Emitter/SapiEmitter.php(27): Laminas\HttpHandlerRunner\Emitter\SapiEmitter->assertNoPreviousOutput() #2 /var/www/sourceturk/forum/vendor/laminas/laminas-httphandlerrunner/src/RequestHandlerRunner.php(98): Laminas\HttpHandlerRunner\Emitter\SapiEmitter->emit() #3 /var/www/sourceturk/forum/vendor/flarum/core/src/Http/Server.php(42): Laminas\HttpHandlerRunner\RequestHandlerRunner->run() #4 /var/www/sourceturk/forum/public/index.php(22): Flarum\Http\Server->listen() #5 {main} thrown in /var/www/sourceturk/forum/vendor/laminas/laminas-httphandlerrunner/src/Exception/EmitterException.php on line 24

matteocontrini

Kyrne A 500 error will be thrown when you disable if the Redis server is turned off before the extension is disabled. This is a conscious decision and was put in place intentionally.

Sorry, what's the reasoning behind that?

I considered this extension a few times but the fact that it sometimes stops the forum from being accessible (for example if Redis is offline) is what stops me from using it.. 😕 I wish it was more resilient, after all it just provides a caching layer that should be optional. Or am I missing something?

Kyrne

2.0.7

Small console command update to improve usability.

Kyrne

matteocontrini there is no easy or fast way to ensure that the forum stays up when redis goes down. I believe building in a Redis down catch is treating a symptom instead of the underlying problem. Redis should be treated like your webserver, instead of making app based fallbacks when it goes down, just don't let it go down.

I do however digress and realize that a lot of people are running forums as hobbies. The latest version has catches to see if redis is down. Keep on mind though that your forum will be a lot slower while it's down.

Finally, the reason it will throw a 500 error if Redis is disabled first is because your users get thrown errors if you kill redis while they are using it (not realistically possible to make a catch for this) and it's there to let you know, "hey, do this in a different order." I'll add it to the docs.

volkan28

we had the same issue. After activating the recache it makes forum stop.

selmanozturk

@Kyrne We have a huge problem with the extension. Let me explain the running environment.

We are serving flarum with nginx + php-fpm 7.2.11 + MariaDb 10.3.17. All of them running in the same host. The host have 20 cpu core, 128gb ram and enough disk space/transfer speed etc. Our main issue is handling the concurrent request. Sometimes we reach 1.5k users online in the forum. Our forum has more than 8 Million discussions.

I can resolve these type of errors above but the system speed getting worse while using plugin. I cant see any problem in the operation of plugin. When it comes to check redis, It also works well with a single instance. After several minutes activating the recache, I can see 10k keys in the redis with about 900 online users.

Here is the average response times:
With recache > 10-12s
Without recache > 4-6s

Do you have any recommendations about this situation?

tankerkiller125

selmanozturk Sometimes we reach 1.5k users online in the forum. Our forum has more than 8 Million discussions.

With numbers like that I would highly recommend running both your MySQL and Redis in a cluster with at least one other server and using a load balance to automatically balance the load and detect if one of the servers goes down. Sometimes having smaller clustered servers is way better performance wise than one super massive beefy server.

Kyrne

tankerkiller125 selmanozturk to add to this, ReCache requires some advanced configuration if you decide to use a cluster. Please message me on Discord if you end up deciding to do this.

I will do a memory leak audit today to see if I can find anything wrong with ReCache. Also, please install the php redis extension, this can alleviate many issues.

matteocontrini

Kyrne there is no easy or fast way to ensure that the forum stays up when redis goes down. I believe building in a Redis down catch is treating a symptom instead of the underlying problem. Redis should be treated like your webserver, instead of making app based fallbacks when it goes down, just don't let it go down.

I do however digress and realize that a lot of people are running forums as hobbies. The latest version has catches to see if redis is down. Keep on mind though that your forum will be a lot slower while it's down.

Finally, the reason it will throw a 500 error if Redis is disabled first is because your users get thrown errors if you kill redis while they are using it (not realistically possible to make a catch for this) and it's there to let you know, "hey, do this in a different order." I'll add it to the docs.

Thanks but... Still not convinced 😃

Let's say that I use a managed Redis cloud service, provided by e.g. DigitalOcean/AWS. It's inevitable that at some point that service will go offline, for maintenance or other faults.

At that point, the forum will keep working but with a higher response time, right? So, if I wanted to avoid having this additional latency while Redis comes up, it is my understanding that if I disable the extension the forum breaks completely.

Is this accurate? Isn't this a plausible and relatively common use case that should be considered?

Thanks 🙂

selmanozturk

tankerkiller125 I tried it before but I didn't have visible performance improvement. I run mysql with clustered mode inside DigitalOcean database. We reach 200k read for each node and system start saturation after that level. I think that issue is about flarum internal(We have almost 9M rows in posts and 77M rows in discussion_user). I don't have enough resource to use mysql cluster with higher number of nodes. Have to find a better solution

selmanozturk

Kyrne I won't planning to use database cluster yet. Do you have any suggestion about the previous question?

« Previous Page Next Page »