Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • 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
  • 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.

...

  1. Measure the time it takes to issue a GET command to read property value from a device (virtual) from a varying number of concurrent clients [1, 10, 20, 50, 100] via Core Command.
  2. Measure the time it takes to issue a PUT command to set a property value on a device (virtual) from a varying number of concurrent clients [1, 10, 20, 50, 100] via Core Command.

...


Device Services

The test cases listed previously can be driven by a Virtual Device Service or device emulator. However, EdgeX also provides a number of Device Service for communicating with real physical devices/sensors. These include:

...