Skip to content

Performance Test#1

Benchmark LeoFS v1.3.0

Purpose

We check Performance with LeoFS

Environment

  • OS: Ubuntu Server 14.04.3
  • Erlang/OTP: 17.5
  • LeoFS: 1.3.0
  • CPU: Intel Xeon E5-2630 v3 @ 2.40GHz
  • HDD (node[36~50]) : 4x ST2000LM003 (2TB 5400rpm 32MB) RAID-0 are mounted at /data/, Ext4
  • SSD (node[36~50]) : 1x Crucial CT500BX100SSD1 mounted at /ssd/, Ext4
 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
 [System Confiuration]
-----------------------------------+----------
 Item                              | Value
-----------------------------------+----------
 Basic/Consistency level
-----------------------------------+----------
                    system version | 1.3.0
                        cluster Id | leofs_1
                             DC Id | dc_1
                    Total replicas | 2
          number of successes of R | 1
          number of successes of W | 1
          number of successes of D | 1
 number of rack-awareness replicas | 0
                         ring size | 2^128
-----------------------------------+----------
 Multi DC replication settings
-----------------------------------+----------
        max number of joinable DCs | 2
           number of replicas a DC | 1
-----------------------------------+----------
 Manager RING hash
-----------------------------------+----------
                 current ring-hash | 1e11048b
                previous ring-hash | 1e11048b
-----------------------------------+----------

 [State of Node(s)]
-------+-------------------------+--------------+----------------+----------------+----------------------------
 type  |          node           |    state     |  current ring  |   prev ring    |          updated at
-------+-------------------------+--------------+----------------+----------------+----------------------------
  S    | S0@192.168.100.36       | running      | 1e11048b       | 1e11048b       | 2016-09-12 17:01:18 +0900
  S    | S10@192.168.100.46      | running      | 1e11048b       | 1e11048b       | 2016-09-12 17:01:18 +0900
  S    | S11@192.168.100.47      | running      | 1e11048b       | 1e11048b       | 2016-09-12 17:01:18 +0900
  S    | S12@192.168.100.48      | running      | 1e11048b       | 1e11048b       | 2016-09-12 17:01:18 +0900
  S    | S13@192.168.100.49      | running      | 1e11048b       | 1e11048b       | 2016-09-12 17:01:18 +0900
  S    | S14@192.168.100.50      | running      | 1e11048b       | 1e11048b       | 2016-09-12 17:01:18 +0900
  S    | S1@192.168.100.37       | running      | 1e11048b       | 1e11048b       | 2016-09-12 17:01:18 +0900
  S    | S2@192.168.100.38       | running      | 1e11048b       | 1e11048b       | 2016-09-12 17:01:18 +0900
  S    | S3@192.168.100.39       | running      | 1e11048b       | 1e11048b       | 2016-09-12 17:01:18 +0900
  S    | S4@192.168.100.40       | running      | 1e11048b       | 1e11048b       | 2016-09-12 17:01:18 +0900
  S    | S5@192.168.100.41       | running      | 1e11048b       | 1e11048b       | 2016-09-12 17:01:18 +0900
  S    | S6@192.168.100.42       | running      | 1e11048b       | 1e11048b       | 2016-09-12 17:01:18 +0900
  S    | S7@192.168.100.43       | running      | 1e11048b       | 1e11048b       | 2016-09-12 17:01:18 +0900
  S    | S8@192.168.100.44       | running      | 1e11048b       | 1e11048b       | 2016-09-12 17:01:18 +0900
  S    | S9@192.168.100.45       | running      | 1e11048b       | 1e11048b       | 2016-09-12 17:01:18 +0900
  G    | G0@192.168.100.35       | running      | 1e11048b       | 1e11048b       | 2016-09-12 17:01:19 +0900
-------+-------------------------+--------------+----------------+----------------+----------------------------

OPS and Latency:

ops-latency

Monitoring Results:

monitoring-results