NodeBB Pods non response after dumping 12 lack data using jmeter scripts


  • We are trying to indentify the NodeBB benchmark for Sunbird Platform

    We are expecting 1200 to 1500 tps for the below infra(specifications)

    NodeBB pods => HPA(autoscaling) from min 2 to 20 pods(each pod 1 core with 1GB memory)
    MongoDB => 16 cores with 32GB memory

    We noticed all userslug api's & topic related POST api's are very low performance.

    We have also noticed For topic create API CPU utilisation of mongod is reaching 100% for 32 cores mongo mechine.

    Find the below MongoDB load over 24 hrs
    7c17d80d-1133-4506-8e9a-f5842c3e7f46-image.png

    Fing the below snapshot of NodeBB load for

    • Topic create API

    • Topic read API's

    With cocurrency 10 & 100
    ce3df3aa-962f-4b2c-a08c-02b5e65679a0-image.png

    Below is the snapshot of API's throuhput & other details of Jemeter script output

    b4ca8bf0-b56d-4792-bf3a-512ee277b7c4-image.png

    Any suggestions/reason why Topic create API is taking 100% CPU usage?

  • GNU/Linux Admin

    @vinu said in NodeBB Pods non response after dumping 12 lack data using jmeter scripts:

    Any suggestions/reason why Topic create API is taking 100% CPU usage?

    Sounds like your database is the bottleneck here, not NodeBB.

    As evidenced by:

    We have also noticed For topic create API CPU utilisation of mongod is reaching 100% for 32 cores mongo mechine.


  • @julian Thanks for the quick response.

    Any suggestions about MongoDB perforamance tunining? Especially for wirte operations?

    We Just tried using both Mongo & Redis, but we have noticed redis is only used to manage user sessions.

    Can we expect better performance, if we switch to Redis instead of MangoDB?

    Hope out team also faced these kind of issues which doing NodeBB benchmarking. Please share if you have any references.


  • @vinu Try using postgresql instead of redis.


  • @volanar @julian
    we are using redis instead of mongoDB
    now we are seeing better throughout

    with redis
    3735c3fb-b63a-4749-8d96-57d6773aa238-image.png

    with mongoDB
    6b2b405f-9e31-4825-b440-993b6e99c4c8-image.png

    CC: @vinu


  • @volanar Thans for the suggestion. After switching to Postgres we are still not getting the better troughput than redis.

    @julian Is it possibl to share the any benchmark results of MongoDB.

    The only option we have now to go with redis(RDB + AOF) with the above results shared by @venkat123 here
    https://community.nodebb.org/post/84368

    Any suggestions on MongoDB, Redis or Postgress config setting to get better performance.

Suggested Topics

| |