What are the advantages of Flarum over Discourse?

Franz

d1a8lo24 At the end there are probably more Flarum installs when Flarums beta was release than there are Discourse forums running.

That's probably not true, to be honest. :-/

BlackSheep

Franz Yeah... Lot of "pros" community are using Discourse. Even if as a UX Designer i feel like they are vomiting in their user mouth, but, eh, that's another debate.

d

malayladu Fastest forum system I have ever seen

See NodeBB if you want to see fast. Discourse is also faster than Flarum. Do not let your passion for Flarum obfuscate some true facts.

Franz

d Discourse is also faster than Flarum.

Do you have some "true facts" to back that up, though? 😃

Kowlin

d I strongly disagree, I will defend NodeBB to death since I absolutely love the community and the software. But Flarum is just faster.

d

Franz I do not want to start a flame war. We tend to be biased towards what we love. Personally I do not run any forum, I only participate on them. I am just interested in technology and follow things that are new; Flarum (F from now on) is one of them.

Based on my own user experience, NodeBB has no match when it comes to speed. It is really hard to beat Redis and NodeJS. F is responsive, but often struggles to render, specially in longer threads, the blank "placeholders" show multiple times. Yet, F is new, barely a beta 2, and has some way to go. I foresee it is bound to get better.

luceos

Well let's see what performance we get using PHP 7 with Redis caching possibly thread/post/user.

accalia

d Discourse is also faster than Flarum

in my experience this is not the case.

for one thing Flarum (and NodeBB for that matter) to my knowledge has never caused someone to write a website just to track performance of the forum.

Discourse has caused such a site to be created: https://servercooties.com/#graph

PJH_

Kowlin I strongly disagree, I will defend NodeBB to death

We're looking to move from Discourse, and one of the potential problems we've noticed with NodeBB is the list of supported databases (only redis, mongo and level to save people looking them up,) none of which would likely be suitable for our forum.

BlackSheep

PJH_ The loading bar at the top of any nodeBB page drive me insane. The Youtube one too. God i hate those things.

d

PJH_ Redis is not really all in memory. I think it will scale just fine to handle your charade, (sticking tongue out).

Filed under: I don't know, therefore I am.

accalia

d Redis is not really all in memory.

We have noticed that yes,

d I think it will scale just fine to handle your charade, (sticking tongue out).

we have been testing it and we have manged, multiple times to cause redis to lock up entirely under usage modes varying from "about normal" to "unholy bot/spam storm"

PJH_

BlackSheep We've yet to find anything immediately suitable as a replacement.

Flarum's use of PATCH without a suitable fallback mechanism is one of it's current problems :-)

d Redis is not really all in memory.

I'm simply deferring to the more knowledgeable denizens of our forum on the matter ;-) One thing that was highlighted:

http://redis.io/topics/faq

Redis is an in-memory but persistent on disk database, so it represents a different trade off where very high write and read speed is achieved with the limitation of data sets that can't be larger than memory.

Franz

d No worries. I was just (and am still) confused about your statement about Discourse being faster than Flarum. That might even be true, but:

there's no benchmark yet (comparing the two on the same server),
it does not confirm my experience, and
most importantly, Discourse wouldn't even run on servers that support Flarum; thus, most Discourse servers you will encounter are bound to be fast (in terms of pure hardware).

Taking my smartypants off now.

d

PJH_ none of which would likely be suitable for our forum

This one test has almost 24,000 posts. Not suitable for your forum?

Kowlin

d Well that test forum just proves my point of NodeBB not being the fastest. 😛

d

Kowlin we past the "fastest" portion already. I was asking @PJH_ about suitability.

dehbuff

flarum is free, and that's more than enough for me 🙂

Personally don't like the design of nodebb and double editor.

Kulga

d
Franz

I apologize but this is kind of useless quibble until as Franz said, they are both run on the same server.
Logically, you cannot run a fair benchmark until they are even. However, you can run a uneven benchmark
that favors one or the other to make a point.

I have a 512MB 2 core VPS. Logically, I should be at a disadvantage with half the needed ram. I'll be comparing it to the primary discourse try it site (which I assume has 1gb+ of ram)
To make it more even, I am clicking on a discussion with 1 post and no added graphics. Then I mimic this for my demo flarum (so it has similar content - which I actually copy multiple times)
There are a lot of reasons why this is not a valid test, so make your own judgements.
Summary:
~400 response time discourse
~180 response time flarum

Edit: Full disclosure - I run the Beta Breaker flarum site tested above and I have personally optimized it. Originally it was getting like 260ms or so and now I (as seen) get about 180ms. I think if you try this site itself, it will load at about 260ms. This kind of brings us full circle back to it's not just about the forum software, but a great amount is webserver config too.

valgrid

I can use flarum with a flaky 30KB/s connection. Discourse not so much. I also like that you can scroll past unloaded posts. That is not possible with discourse as far as i know. You have to load all the comments in between immediately, because the software only scrolls to end of the loaded comments.

« Previous Page Next Page »