"Mark all as read" Memory Usage?

General Discussion
  • Looking for some input/feedback.

    I'm running NodeBB on Heroku and RedisToGo. After a large data import (tens of thousands of posts) when I log in as any user and click into "Unread" and "Mark all as read" the memory usage on both the server and Redis instance spikes. In my case I'm still running in test mode with just 512MB in redis (it usually sits at 309 used or so) and 512MB of memory on a basic Heroku dyno.

    Basically the dyno grinds to a halt from swapping and the redis sends an alert about being over quota. Once I kill the dyno memory in Redis drops back down, and of course the restarted dyno doesn't resume the operation.

    Is this behavior expected? Do I just need to allocate more memory to allow the operation to complete without blowing out my resource quotas? Is there any way to just flag all posts as read by all users as a starting point since I'm guessing it's trying to mark tens of thousands of posts as read all in one operation?


  • Hey @medwards are you on latest? We recently changed mark all read so it only marks the topics in the last month as read instead of going through all topics.

  • @baris

    I'm currently running a patched version of 0.3.2 I think.

    I'll try to upgrade and see if it fixes it.

  • @baris

    That does appear to resolve the issue. One issue it brings up, though, is that I have customizations to the lavender theme and the version I've been using appears incompatible with Edge.

    Is there any way to identify which versions of the lavender theme are compatible with which versions of NodeBB?

Suggested Topics

  • 0 Votes
    6 Posts

    @baris i take your plugin "browsing-users" and create a new one "who-read-it". I hope it is okay for you 🐞

    currently it looks like this:


    the timestamp i like to have in the tooltip behind the username, but i dont know who, maybe you have a idea?

    <div component="topic/who-read-it" class="d-flex gap-1"> <i class="fa fa-check fa-fw" title="Who Read It"></i> <br> {{{ each whoreadit }}} <div data-uid="{./uid}"> <a class="text-decoration-none" href="{{{ if ./userslug }}}{config.relative_path}/user/{./userslug}{{{ else }}}#{{{ end }}}"> {buildAvatar(whoreadit, "24px", true, "avatar-tooltip","title=test")}{./readtimestamp} </a> </div> {{{ end }}} </div>
  • 1 Votes
    1 Posts

    This forum support infinite scroll, it wonderful, but sometimes it's annoying. Open long duscussion (with 300-400 answers) is painful, I open read only last few answers and if scroll to top (look at topic theme or breadcrumbs) , I cant do it, because forum load previous pages. It's very annoying for me.

    It's possible add button "load more"? I see it this way: when user open topic first time, he see only one page (20 posts for example) and if topic has more posts, buttons "load more" (at top if exist earlier posts and bottom if exists later posts). If user press once "load more" - means we activate infinite scroll as it works now.

    Pagination with infinite scroll (better solution than "load more")

    Best infinite scroll i meet: https://vk.com/topic-200_2806586

    Above discussion placed pagination and when you scroll, work infinite scroll. But scroll work only in direct side, not when you scroll back. For example if user open first page he can read whole discussion with infinite scroll. If he scroll back, its return to first page (where he start reading)

    If he open 5th page he can also read to the end. But if he scroll back, in this case he return to 5th page (where he start reading).

    So if user open last page (most common case for forum, read last unread post), infinite scroll doesn't work at all. If unread posts several(2 pages, for example), user open last but one page and infinite scroll works only work with 2 last pages.

    Hope you understand idea. You can play with VK demo:
    Topic from first page
    last but one page
    latest page

    My js skill not enough to implement this, so I can only offer idea.

  • 2 Votes
    7 Posts

    The author also could create a new post stating that some changes have been made if it's worth an update in his opinion. I don't think any other concept is needed since editing posts is more wiki-like than forum-like. If your forum relies on something like this you might consider using a wiki platform instead or additionally.

  • Is node.js "dying"?

    General Discussion
    3 Votes
    25 Posts

    @yariplus I could have sworn you just said Lisp XD

  • 0 Votes
    27 Posts

    okay 🙂 FYI there's a robots.txt editor in the ACP if you really didn't want it to show up on google search 🙂