6.12. Massively Distributed RPCs report

Below there are the results of the test plan of massively distributed RPCs.

6.12.1. Test Environment

6.13. Environment Description

Paravance cluster (72 nodes) of Rennes site at Grid’5000 testbed.

Model

Dell PowerEdge R630

CPU

Intel Xeon E5-2630 v3 Haswell 2.40GHz (2 CPUs/node, 8 cores/CPU)

Memory

128 GB

Storage

558 GB HDD SATA ST600MM0006 (x2)

driver: ahci

Network

eth0/eno1, Ethernet

configured rate: 10 Gbps

model: Intel 82599ES 10-Gigabit SFI/SFP+ Network Connection

driver: ixgbe

eth1/eno2, Ethernet

configured rate: 10 Gbps

model: Intel 82599ES 10-Gigabit SFI/SFP+ Network Connection

driver: ixgbe

OS

Debian 9 “Stretch”

oslo.messaging

5.35.0

pyngus

2.2.2

ombt

2.3.0 (a3f0fc7)

ombt-orchestrator

1.x

broker

RabbitMQ server 3.6.x

router

QP dispatch server 1.0.1

topology

complete_graph (router only)

6.13.1. Test Case 1

6.13.1.1. Latency

6.13.1.1.1. Driver and Call Type

Driver

Instances

Type

Messages

Latency

Distribution

broker

1

rpc-call

bm1l

bl1l

bd1l

broker

1

rpc-cast

bm1t

bl1t

bd1t

router

1

rpc-call

rm1l

rl1l

rd1l

router

1

rpc-cast

rm1t

rl1t

rd1t

broker

3

rpc-call

bm3l

bl3l

bd3l

broker

3

rpc-cast

bm3t

bl3t

bd3t

router

3

rpc-call

rm3l

rl3l

rd3l

router

3

rpc-cast

rm3t

rl3t

rd3t

broker

5

rpc-call

bm5l

bl5l

bd5l

broker

5

rpc-cast

bm5t

bl5t

bd5t

router

5

rpc-call

rm5l

rl5l

rd5l

router

5

rpc-cast

rm5t

rl5t

rd5t

6.13.1.1.2. Driver distribution comparison against number of clients

Clients

rpc-call

rpc-cast

1000

 ../../_images/latency-rpc-call_1000.png ../../_images/latency-rpc-cast_1000.png

2000

 ../../_images/latency-rpc-call_2000.png ../../_images/latency-rpc-cast_2000.png

4000

 ../../_images/latency-rpc-call_4000.png ../../_images/latency-rpc-cast_4000.png

6000

 ../../_images/latency-rpc-call_6000.png ../../_images/latency-rpc-cast_6000.png

8000

 ../../_images/latency-rpc-call_8000.png ../../_images/latency-rpc-cast_8000.png

10000

 ../../_images/latency-rpc-call_10000.png ../../_images/latency-rpc-cast_10000.png

6.13.1.2. RPC-CALL metrics

Metric results show maximum (collected) values for each case.

6.13.1.2.1. Memory usage on the bus

Driver

Instances

Memory

broker

1

 ../../_images/usage_mem_bus-1-rabbitmq_0-rpc-call.png

router

1

 ../../_images/usage_mem_bus-1-router_0-rpc-call.png

broker

3

bm30l bm31l bm32l

router

3

rm30l rm31l rm32l

broker

5

bm50l bm51l bm52l bm53l bm54l

router

5

rm50l rm51l rm52l rm53l rm54l

6.13.1.2.2. CPU usage on the bus

Driver

Instances

CPU

broker

1

 ../../_images/usage_cpu_percent_bus-1-rabbitmq_0-rpc-call.png

router

1

 ../../_images/usage_cpu_percent_bus-1-router_0-rpc-call.png

broker

3

bc30l bc31l bc32l

router

3

rc30l rc31l rc32l

broker

5

bc50l bc51l bc52l bc53l bc54l

router

5

rc50l rc51l rc52l rc53l rc54l

6.13.1.2.3. TCP connections on the bus

Driver

Instances

TCP connections

broker

1

 ../../_images/tcp_established_bus-1-rabbitmq_4-rpc-call.png

router

1

 ../../_images/tcp_established_bus-1-router_4-rpc-call.png

broker

3

bt30l bt31l bt32l

router

3

rt30l rt31l rt32l

broker

5

bt50l bt51l bt52l bt53l bt54l

router

5

rt50l rt51l rt52l rt53l rt54l

6.13.1.2.4. Network traffic on the bus

Driver

Instances

Type

TCP connections

broker

1

Sent

 ../../_images/net_sent_bus-1-rabbitmq_2-rpc-call.png

broker

1

Recv

 ../../_images/net_recv_bus-1-rabbitmq_2-rpc-call.png

router

1

Sent

 ../../_images/net_sent_bus-1-router_2-rpc-call.png

router

1

Recv

 ../../_images/net_recv_bus-1-router_2-rpc-call.png

broker

3

Sent

bo30l bo31l bo32l

broker

3

Recv

bi30l bi31l bi32l

router

3

Sent

ro30l ro31l ro32l

router

3

Recv

ri30l ri31l ri32l

broker

5

Sent

bo50l bo51l bo52l bo53l bo54l

broker

5

Recv

bi50l bi51l bi52l bi53l bi54l

router

5

Sent

ro50l ro51l ro52l ro53l ro54l

router

5

Recv

ri50l ri51l ri52l ri53l ri54l

6.13.1.3. RPC-CAST metrics

Metric results show maximum (collected) values for each case as previous case.

Note that the max of Y range is not the same as metrics of RPC-CALL.

6.13.1.3.1. Memory usage on the bus

Driver

Instances

Memory

broker

1

 ../../_images/usage_mem_bus-1-rabbitmq_0-rpc-cast.png

router

1

 ../../_images/usage_mem_bus-1-router_0-rpc-cast.png

broker

3

bm30t bm31t bm32t

router

3

rm30t rm31t rm32t

broker

5

bm50t bm51t bm52t bm53t bm54t

router

5

rm50t rm51t rm52t rm53t rm54t

6.13.1.3.2. CPU usage on the bus

Driver

Instances

CPU

broker

1

 ../../_images/usage_cpu_percent_bus-1-rabbitmq_0-rpc-cast.png

router

1

 ../../_images/usage_cpu_percent_bus-1-router_0-rpc-cast.png

broker

3

bc30t bc31t bc32t

router

3

rc30t rc31t rc32t

broker

5

bc50t bc51t bc52t bc53t bc54t

router

5

rc50t rc51t rc52t rc53t rc54t

6.13.1.3.3. TCP connections on the bus

Driver

Instances

TCP connections

broker

1

 ../../_images/tcp_established_bus-1-rabbitmq_4-rpc-cast.png

router

1

 ../../_images/tcp_established_bus-1-router_4-rpc-cast.png

broker

3

bt30t bt31t bt32t

router

3

rt30t rt31t rt32t

broker

5

bt50t bt51t bt52t bt53t bt54t

router

5

rt50t rt51t rt52t rt53t rt54t

6.13.1.3.4. Network traffic on the bus

Driver

Instances

Type

TCP connections

broker

1

Sent

 ../../_images/net_sent_bus-1-rabbitmq_2-rpc-cast.png

broker

1

Recv

 ../../_images/net_recv_bus-1-rabbitmq_2-rpc-cast.png

router

1

Sent

 ../../_images/net_sent_bus-1-router_2-rpc-cast.png

router

1

Recv

 ../../_images/net_recv_bus-1-router_2-rpc-cast.png

broker

3

Sent

bo30t bo31t bo32t

broker

3

Recv

bi30t bi31t bi32t

router

3

Sent

ro30t ro31t ro32t

router

3

Recv

ri30t ri31t ri32t

broker

5

Sent

bo50t bo51t bo52t bo53t bo54t

broker

5

Recv

bi50t bi51t bi52t bi53t bi54t

router

5

Sent

ro50t ro51t ro52t ro53t ro54t

router

5

Recv

ri50t ri51t ri52t ri53t ri54t