Confirming FineBI Node Quantity​

  • Last update: 2024-04-24

    • Overview 

    Clustered FanRuan projects (nodes) are supported. Determine the appropriate number of main application servers based on the scenario.

    This document provides recommended configurations for three scenarios. For FanRuan projects involving multiple scenarios, choose the highest configuration as the recommended configuration.

    Note 1: The FanRuan project deployed via FineOps can have one to five nodes.

    Note 2: The following table explains different user types.

    User TypeDescription
    Number of Daily Active Users (DAUs)Number of users who log in to the FineBI project within one day
    Number of Online UsersNumber of logged-in users in FineBI at a certain moment
    Number of Concurrent Users

    Number of users who operate in FineBI at a certain moment

    It represents how many users send requests to the server at the same time, namely how many requests the server handles at the same time.

    Concurrency Limit During License Registration

    Maximum number of system-accessed IP addresses (rather than the user quantity) obtained by the server from requests (as concurrent keys)

    This parameter for license registration has no correlation with the number of users in the following text.

    Direct Connect Data 

    Scenario description: The FineBI project only uses direct-connected data, and does not use extracted data.

    The bandwidth among cluster nodes, nodes, and other components is 1000 Mb/s.

    Number of Daily Active Users (DAUs)

    Number of Online Users Per Hour

    Number of Concurrent Users Per Second

    Number of Concurrent Edits

    Number of Calculations Processed Per Second

     (Data Source Calculation Capability)

    		Recommended ConfigurationMinimum Configuration
    500＜100＜20＜20＜10

    Single-node project, in which the node should meet the following configuration:

    CPU: 8 cores, 16 threads, 2.5 GHz

    JVM memory: 16 GB

    Physical memory: 24 GB

    Single-node project, in which the node should meet the following configuration:

    CPU: 4 cores, 8 threads, 2.5 GHz

    JVM memory: 8 GB

    Physical memory: 12 GB

    2K100~1K40~9010~4010~20

    Two-node cluster, in which each node should meet the following configuration:

    CPU: 16 cores, 32 threads, 2.5 GHz

    JVM memory: 16 GB

    Physical memory: 32 GB

    Single-node project, in which the node should meet the following configuration:

    CPU: 16 cores, 32 threads, 2.5 GHz

    JVM memory: 16 GB

    Physical memory: 24 GB

    3K600~1.5K60~13030~60≥30

    Three-node cluster, in which each node should meet the following requirements:

    CPU: 16 cores, 32 threads, 2.5 GHz

    JVM memory: 16 GB

    Physical memory: 24 GB

    Two-node cluster, in which each node should meet the following configuration:

    CPU: 16 cores, 32 threads, 2.5 GHz

    JVM memory: 24 GB

    Physical memory: 48 GB

    4K600~2K60~17060~80≥30

    Four-node cluster, in which each node should meet the following requirements:

    CPU: 16 cores, 32 threads, 2.5 GHz

    JVM memory: 16 GB

    Physical memory: 24 GB

    Three-node cluster, in which each node should meet the following requirements:

    CPU: 16 cores, 32 threads, 2.5 GHz

    JVM memory: 24 GB

    Physical memory: 48 GB

    Extracted Data: Self-Service Analysis of High-DAU FineBI Projects 

    Scenario description: The DAU of the FineBI project is high, and users can analyze data by themselves.

    Disk throughput and bandwidth need to be greater than 100 MB/s (namely performance of normal HDDs). SSDs are recommended.

    JVM memory is not the same as the whole device memory. You are advised to set the JVM memory to 2/3 to 3/4 of the total device memory.

    Number of Online Users Per Hour

    Number of Concurrent Users Per Second

    Number of Concurrent Edits

    Table Quantity/Size

    		Recommended ConfigurationMinimum Configuration
    ＜100＜20＜20＜100/＜1T

    Standalone project, in which the node should meet the following requirements:

    CPU: 8 cores, 16 threads, 2.5 GHz

    JVM memory: 16 GB

    Physical memory: 32 GB

    Standalone project, in which the node should meet the following requirements:

    CPU: 8 cores, 16 threads, 2.5 GHz

    JVM memory: 16 GB

    Physical memory: 32 GB

    300~100020~7010~40＜100/＜1T

    Two-node cluster, in which each node should meet the following configuration:

    CPU: 8 cores, 16 threads, 2.5 GHz

    JVM memory: 16 GB

    Physical memory: 32 GB

    Standalone project, in which the node should meet the following requirements:

    CPU: 16 cores, 32 threads, 2.5 GHz

    JVM memory: 32 GB

    Physical memory: 64 GB

    600~200040~12030~60＞2000/＞1T

    Two-node cluster, in which each node should meet the following configuration:

    CPU: 16 cores, 32 threads, 2.5 GHz

    JVM memory: 32 GB

    Physical memory: 64 GB

    Two-node cluster, in which each node should meet the following configuration:

    CPU: 16 cores, 32 threads, 2.5 GHz

    JVM memory: 24 GB

    Physical memory: 48 GB

    900~300050~16050~80＞4000/＞2T

    Three-node cluster, in which each node should meet the following requirements:

    CPU: 16 cores, 32 threads, 2.5 GHz

    JVM memory: 32 GB

    Physical memory: 64 GB

    Two-node cluster, in which each node should meet the following configuration:

    CPU: 16 cores, 32 threads, 2.5 GHz

    JVM memory: 24 GB

    Physical memory: 48 GB

    1200~350060~19070~100＞5000/＞3T

    Four-node cluster, in which each node should meet the following requirements:

    CPU: 16 cores, 32 threads, 2.5 GHz

    JVM memory: 32 GB

    Physical memory: 64 GB

    Three-node cluster, in which each node should meet the following requirements:

    CPU: 16 cores, 32 threads, 2.5 GHz

    JVM memory: 32 GB

    Physical memory: 64 GB

    1500~400080~22080~200＞5000/＞3T

    Five-node cluster, in which each node should meet the following requirements:

    CPU: 16 cores, 32 threads, 2.5 GHz

    JVM memory: 32 GB

    Physical memory: 64 GB

    Four-node cluster, in which each node should meet the following requirements:

    CPU: 16 cores, 32 threads, 2.5 GHz

    JVM memory: 32 GB

    Physical memory: 64 GB

    Extracted Data: Concurrently Viewing Dashboards 

    Scenario description: FineBI users concurrently view dashboards and the like.

    When the number of request users per second reaches 160, the download speed of the load-balancing server needs to reach 100 MB/s.

    JVM memory is not the same as the whole device memory. You are advised to set the JVM memory to 2/3 to 3/4 of the total device memory.

    Number of Concurrent Users Every Five Minutes


    Number of Concurrent Users Per Second

    Recommended Configuration

    Minimum Configuration

    ~40040Two-node cluster, in which each node should meet the following configuration:

    CPU: 8 cores, 16 threads, 2.5 GHz

    JVM memory: 16 GB

    Physical memory: 32 GB

    Standalone project, in which the node should meet the following requirements:

    CPU: 16 cores, 32 threads, 2.5 GHz

    JVM memory: 32 GB

    Physical memory: 64 GB

    400~80080

    Two-node cluster, in which each node should meet the following configuration:

    CPU: 16 cores, 32 threads, 2.5 GHz

    JVM memory: 32 GB

    Physical memory: 64 GB

    Two-node cluster, in which each node should meet the following configuration:

    CPU: 16 cores, 32 threads, 2.5 GHz

    JVM memory: 24 GB

    Physical memory: 48 GB

    800~1100110

    Three-node cluster, in which each node should meet the following configuration:

    CPU: 16 cores, 32 threads, 2.5 GHz

    JVM memory: 32 GB

    Physical memory: 64 GB


    Three-node cluster, in which each node should meet the following configuration:

    CPU: 16 cores, 32 threads, 2.5 GHz

    JVM memory: 24 GB

    Physical memory: 48 GB


    1100~1600160

    Four-node cluster, in which each node should meet the following configuration:

    CPU: 16 cores, 32 threads, 2.5 GHz

    JVM memory: 32 GB

    Physical memory: 64 GB

    Three-node cluster, in which each node should meet the following configuration:

    CPU: 16 cores, 32 threads, 2.5 GHz

    JVM memory: 32 GB

    Physical memory: 64 GB

    1600~2000190

    Five-node cluster, in which each node should meet the following configuration:

    CPU: 16 cores, 32 threads, 2.5 GHz

    JVM memory: 32 GB

    Physical memory: 64 GB

    Four-node cluster, in which each node should meet the following configuration:

    CPU: 16 cores, 32 threads, 2.5 GHz

    JVM memory: 32 GB

    Physical memory: 64 GB


    Attachment List


    Theme： 部署新项目
    Previous
    Next
    • Helpful
    • Not helpful
    • Only read
    中文（繁體） 中文（简体）
    English