...
- Footprint – tests that measure both the executable file size and docker image size on disk for each EdgeX microservice.
- Memory – tests that measure the memory (RAM) consumed by each running EdgeX microservice for different load conditions. For example, measure the memory consumed when varying number of concurrent EdgeX Devices writing data into EdgeX, with varying data payload (Event/Reading collections) sizes and sampling rates.
- Service Startup - TO BE COMPLETED tests that measure how long it takes for each EdgeX microservice to startup.
- Latency – tests that measure the time it takes to take specific actions using EdgeX for different load conditions. For example, measure the time it takes for an EdgeX Device to read a data value and then export the same data value via the Export Service.
- CPU – tests that measure the CPU consumed (as a % of total CPU availability) when running EdgeX microservice under different load conditions.
- Throughput – tests that measure the data throughout (bytes/second) that can be achieved from data being read by an EdgeX Device to the data being exported via the Export Service for different load conditions.
...
- Measure the memory (RAM) in bytes consumed by each EdgeX Microservices microservice in their idle state (running but no data flowing through the system).
- Measure the memory (RAM) in bytes consumed by each EdgeX Microservices microservice with [1, 10, 20, 50, 100] devices, reading an event with [1, 5, 10, 50, 100] readings at a sample rate of [100 ms, 1 sec, 10 sec, 30 sec, 60sec].
Service Startup TO BE COMLETEDStartup
- Measure the time it takes to startup each EdgeX microservice, this includes the time it tales to create the docker container, configure and initialize the service.
Latency
- Measure the time it takes to read an event with [1, 5, 10, 50, 100] readings from [1, 10, 20, 50, 100] devices (virtual) with a sample rate of [100 ms, 1 sec, 10 sec, 30 sec, 60sec] and export it (via the Export Service).
...