How much can NodeBB run on

General Discussion
  • On the Openshift free plan, how much users, topics, categories, and posts can a NodeBB forum handle?

    I checked the gear usage on a fresh NodeBB install and it appears 0.7 GB out of 1 GB is already used up. So only 300 MB is left.

  • I'd suggest at least 1GB, especially if you're running the db on the same machine, and you should turn swap on in case it rises above that (for npm installs, and so you can at least log in if memory gets too high) 2GB should give you plenty of breathing room

  • @Bri How much users can it handle? How much posts? How much can it overall handle?

  • @Bri

    i've seen articles stating that wp can run with big user spike and traffic on nginx 512mb without any problem so i would be very surprised if nodebb 500-1000 active users can't handle 512mb.

    can anyone confirm or provide some figures?

  • I know that @scottalanmiller is running a relatively high traffic forum on nodebb.

    A lot depends on various factors like if you're running a CDN, what plugins you're running, and any other processes running on the node.

    On my setup, I was running a cluster of three, with a gocamo server, along with redis (for session storage) and mongo, along with (at the time) mysql.

Suggested Topics

  • 0 Votes
    1 Posts

    How do I migrate a forum from phpBB 3.0.9 to nodeBB 1.14.2?

    I've found some plugins but I'm pretty sure the version differences will cause major headaches :

    (importer wrong phpBB and nodeBB verions) : (migration exporter ? ) : (exporter closest version match but not quite : pbpBB 3.1 ) :

    (post migration, convert to markdown ) :

    Also I'm not quite sure of the procedure?

    Is it remote connect to the phpBB server stop the forum and install the exporter plugin then start the forum and pick up the entire forum as one database file, then stop new nodeBB forum install plugin then start the new forum and import the file?

    it's unclear from what's given.

    I also have some perhaps unusual requirements :

    I'm not interested in migrating accounts, in fact I specifically do not want to migrate accounts. the migration exists only as comfort for those who want to be able to look up the old archived threads (btw I will mark them all as read-only after migration) but effectively we are starting from scratch with new accounts.

    So I'm not interested in migrating the accounts and I'm wondering if that's an issue? do posts necessarily need to be created with an account or is creating posts made by an unattributed user name possible? (if nodeBB attributes posts from the old forum archive to a new forum joinee that's perfectly fine by me, not so if nodeBB refuses that a new joinee use that name under pretext that it's already under use. New users and content must take priority)

    will nodeBB allow this or will it require a account named "archivebot" for example to be "responsible", the "author" of all these posts. I'd prefer if I could at least preserve the author names buit if I can't that's an ok sacrifice.

    Also will nodeBB allow the original dates for the posts? or will all of them be of the date of the migration?

    TLDR: I don't know how to migrate from phpBB 3.0.9 to nodeBB 1.14.2 specifically there doesn't seem to be an upgrade path for those specific version numbers.

  • 0 Votes
    8 Posts


    Yes, figured that out the hard way lol

  • 0 Votes
    1 Posts

    I did Restart of my Nodebb Forum and now don't work the Panel of Admin.
    I have this Plugins :

    O.S : Windows Server 2012
    Nodebb Version : 0.6.0

  • 0 Votes
    4 Posts

    @pitaj said:

    @Master-Antonio add your domain in the config.json file which sits in the NodeBB main directory.

    Did, but don't work.

  • 0 Votes
    4 Posts

    @avi Hard to say, they could be doing it through cookies, if you upvote a deal, the upvote of that deal is saved into your cookies, then if you try again in the same browser, it knows you've done it already, however this is also circumventable by changing browsers and deleting your browser cookies. You can make it hard for someone to fake votes, but you can't stop it.

    I think a mixture of email confirmation, cookie usage, limiting who can upvote and downvote (need to post a deal in order to vote for other deals, or something like that) and keeping an eye on activity would deter enough people not to bother trying to fake the votes.

    You'd have to post the deal, log out, clear your entire browser cache, cookies, history etc, create an email account, sign up, verify your account, upvote, then do the whole thing again, the time taken isn't worth it, it would be easier to hire a team of people in the east to do it for you (similar to likes on facebook or views on youtube), and you can't stop them unless you place blanket IP bans on subnet ranges. Which, if you're only concentrating on one place, then that would be fine.