Performance Test

Test Machine

Name	DeviceOn/ePaper	vCPU	Memory (GB)
Azure Virtual Machine Standard D2s v5	v3.2.0	2	8
Azure Virtual Machine Standard D4s v5	v3.2.0	4	16

Connection & Auto-report Test

Test Condition

We performed stress tests utilizing Azure virtual machines (Standard D2s v5 and Standard D4s v5) with different quantities of EPD devices, connecting them to the server within a one-hour window. During the test, each device continuously transmitted report data at one-minute intervals, assessing the system's capacity to handle ongoing data reporting under varying loads.

Summary

The Standard D2s v5 and Standard D4s v5 virtual machines are capable of supporting up to 2,500 and 7,000 devices per hour, respectively, providing scalable performance to meet varying operational demands.

Results

• Standard D2s v5

Connected Devices	Auto-report	Time	Result	Note
2500	1 min	1 hr	Success
3000	1 min	1 hr	Failed	Packet loss in MongoDB, receiving 98.5% of the data.

• Standard D4s v5

Connected Devices	Auto-report	Time	Result	Note
5000	1 min	1 hr	Success
7000	1 min	1 hr	Success
8000	1 min	1 hr	Failed	Packet loss in MongoDB, receiving 98.9% of the data.
10000	1 min	1 hr	Failed

Transmit Image Schedule Test

Test Condition

We performed tests using Azure virtual machines with different quantities of EPD devices, transmitting 2MB images over intervals of 10 minutes, 30 minutes, and 1 hour. These tests aimed to evaluate the system's performance under varying transfer loads and to determine the maximum number of EPD devices that could be supported efficiently during image transmission.

Summary

• D2s v5:

  • Maximum supported devices for the 10-minute image transfer schedule: 500

  • Maximum supported devices for the 30-minute image transfer schedule: 1,400

• D4s v5:

  • Maximum supported devices for the 10-minute image transfer schedule: 800

  • Maximum supported devices for the 30-minute image transfer schedule: 2,000

  • Maximum supported devices for the 1-hour image transfer schedule: 3,500

Results

• Standard D2s v5 for the 10-minutes schedule

Connected Devices	Time per batch	Batch	Result	Note
200	3 min	104	Success
500	7 min	30	Success
700	9 min	18	Failed	Packet loss in MongoDB, receiving 98.16% of the data.

• Standard D2s v5 for the 30-minutes schedule

Connected Devices	Time per batch	Batch	Result	Note
1400	21 min	15	Success
1600	21 min	16	Failed	Packet loss in MongoDB, receiving 99.15% of the data.
1800	24 min	9	Failed
2000	27 min	4	Failed	Packet loss in MongoDB, receiving 97.52% of the data.

• Standard D4s v5 for the 10-minutes schedule

Connected Devices	Time per batch	Batch	Result	Note
800	9 min	24	Success
900	11 min	4	Failed	Time per batch exceeds 10-minutes schedule

• Standard D2s v5 for the 30-minutes schedule

Connected Devices	Time per batch	Batch	Result	Note
2000	22 min	28	Success
2500	37 min	1	Failed	Time per batch exceeds 30-minutes schedule

• Standard D4s v5 for the 1-hr schedule

Connected Devices	Time per batch	Batch	Result	Note
3500	41 min	12	Success
4000	47 min	3	Failed	Packet loss in MongoDB after 3 hours
5000	-	1	Failed