MDTM Evaluation @ ESNET 100G Testbed

The MDTM research team works with ESNET network engineers to test and evaluate mdtmFTP on ESNET 100G testbed. We compared mdtmFTP with existing data transfer tools--GridFTP, BBCP, and FDT--in various scenarios. It demonstrates that mdtmFTP achieves better data transfer performance than these tools.

1.    Evaluation Configuration

As shown in Figure 1, the evaluation will be carried out in ESNET 100G test bed. We run data transfer from DTN nersc-tbn-2 to nersc-tbn-1. There is a 95ms RTT loop between nersc-tbn-1 and nersc-tbn-2.

Figure 1 ESNET 100G Test bed

DTN nersc-tbn-1

This DTN is designed for high performance I/O operations. This DTN I/O is based on an array of 24 HDD's. The HDD's are connected to one RAID controller, creating a single RAID0 set. The HDD has a maximum disk I/O of 20-25 Gbps (read) and 12 Gbps (write). nersc-tbn-1 is connected to the router, nersc-tb-1, with 2 x 40G and 4 x 10G NICs. The DTN has a maximum network I/O of 80 Gbps.

DTN nersc-tbn-2

This DTN is designed for high performance I/O operations. nersc-tbn-2 is based on an array of 24 SSD's. The SSD's are connected to two RAID controllers, 12 SDD's each. Each RAID controller is configured with one RAID0 sets, of 12 SSD each. It has a maximum storage I/O of 80-85 Gbps (read). nersc-tbn-2 is connected to the router, nersc-tb-1, with 2 x 40G and 4 x 10G NICs. It has a maximum network I/O of 80Gbps.

 

2.    Evaluation Methodology

  • Transfer data from nersc-tbn-2 to nersc-tbn-1

  • Performance metric: Time-to-Completion

  • Comparing data transfer tools
  • Transfer Mode
    • Client-Server data transfer
    • 3rd-party data transfer
  •  
  • Evaluation Scenarios
    • Large file transfer: Transfer a 100GB file from nersc-tbn-2 to nersc-tbn-1
    • Folder transfer 1: Transfer a folder, which has 30 10G files, from nersc-tbn-2 to nersc-tbn-1
    • Folder transfer 2: Transfer a Linux-3.18.21 folder, which has millions of files, from nersc-tbn-2 to nersc-tbn-1

  • Data transfer tool configuration

Data transfer tools

# of parallel streams

Pipelining

Concurrency

TCP parameters

FDT

4

N/A

N/A

System Config

GridFTP

4

-PP

-CC 8

System Config

BBCP

4

N/A

N/A

System Config

mdtmFTP

4

N/A

N/A

System Config

Table 1 Data transfer tool configuration

 

3.    Evaluation results

  • Client/Server data transfer -- Large file data transfer (1x100GB)

 

mdtmFTP

FDT

GridFTP

BBCP

Time-to-completion (seconds)

74.18

79.89

91.18

Very poor

Table 2. Large file data transfer -- 1x100GB (smaller is better)

 

Figure 2 Large File Data Transfer -- 1x100GB (larger is better)

  • Client/Server data transfer -- Folder data transfer 1 (30x10GB)

 

mdtmFTP

FDT

GridFTP

BBCP

Time-to-completion (seconds)

192.19

217

320.17

Very poor

Table 3. Folder data transfer -- 30x10GB (smaller is better)

Figure 3 Folder data transfer -- 30x10GB (larger is better)

 

  • Client/Server data transfer -- Folder data transfer 2 (Linux 3.12.21)

 

mdtmFTP

FDT

GridFTP

BBCP

Time-to-completion (seconds)

10.51

Failed

1006.02

Very poor

Table 4. Folder data transfer -- Linux 3.12.21 (smaller is better)

 

Figure 4 Folder data transfer -- Linux 3.12.21 (larger is better)

 

  • 3rd party data transfer -- Large file data transfer (1x100GB)

 

mdtmFTP

FDT

GridFTP

BBCP

Time-to-completion (seconds)

34.976

N/A

106.84

N/A

Table 5 Large file data transfer - 1x100GB (smaller is better)

 

Figure 5 Large file data transfer -- 1x100GB (larger is better)

 

  • 3rd party data transfer -- folder data transfer 1 (30x10GB)

 

mdtmFTP

FDT

GridFTP

BBCP

Time-to-completion (seconds)

95.61

N/A

Not supported

N/A

Table 6 Folder data transfer -- 30x10GB (smaller is better)

 

  • 3rd party data transfer -- folder data transfer 2 (Linux 3.12.21)

 

mdtmFTP

FDT

GridFTP

BBCP

Time-to-completion (seconds)

9.68

N/A

Not supported

N/A

Table 7 Folder data transfer -- Linux 3.12.21 (smaller is better)

 

Note: BBCP and FDT support 3rd party data transfer. But BBCP and FDT cannot run 3rd party data transfer on ESNET testbed due to testbed limitation.

    • Last modified
  • 07/08/2016