All documents

FPT MongoDB Enterprise

    Sysbench benchmark results
    Sysbench benchmark results
    Updated on 15 May 2026

    This section presents database cluster performance benchmark results performed using the Sysbench tool, aiming to provide a reference for the processing capabilities of database engines across different compute configurations (flavors).

    The results are provided for reference purposes only and do not represent guaranteed performance.

    1. Benchmark sysbench overview

    Purpose:

    • Evaluate OLTP (Read/Write) performance of supported database engines.
    • Observe performance scaling behavior when increasing CPU and memory resources.
    • Provide reference data to assist customers in selecting appropriate instance sizes.

    Metrics:

    • Sysbench Read: Total number of read queries executed during the test.
    • Sysbench Write: Total number of write queries executed during the test.
    • QPS (Queries Per Second): Average number of queries processed per second.
    • TPS (Transactions Per Second): Average number of completed transactions per second.

    Higher QPS and TPS values indicate higher throughput under the tested workload.

    2. Benchmark results

    Test environment:

    Parameter Value
    Benchmark tool Sysbench (OLTP Read/Write)
    Number of documents 1.000.000
    Number of operations 1.000.000
    Workload type Read/Write
    Thread count (YCSB threads) Configurations correspond to each flavor.
    MongoDB version MongoDB Enterprise v8.0.20-ent
    IOPS 6000

    Result:

    Flavor (vCPU/RAM) Thread count Sysbench Read Sysbench Write QPS TPS
    2C4G 8 500310 499690 4083.95 4083.95
    2C8G 8 500652 499348 5120.56 5120.56
    4C8G 16 499868 500132 9007.79 9007.79
    8C16G 32 501398 498602 17666.6 17666.66
    8C32G 64 500420 499529 21993.49 21993.49
    16C32G 64 499522 500478 31626.55 31626.55
    16C64G 128 500086 499914 34621.24 34621.24

    3. Analysis & Recommendations

    • Increasing CPU and memory generally improves throughput.
    • Performance gains may diminish at higher configurations depending on workload and system limits.

    Important:

    • Benchmark results are workload-specific and provided for reference only.
    • Actual performance may vary depending on:
      • Application workload characteristics.
      • Database schema and indexing.
      • Read/write ratio.
      • Storage and network configuration.

    Customers are strongly encouraged to test with their own workloads before deploying to production.

    Recommendations:

    Use these benchmark results as guidance when selecting database engines and instance sizes. For optimal performance, validate configuration choices through application-specific performance testing.