物联网数据的纯粹范围会影响应用程序的物联网性能测试。最佳性能测试可以使用IoT应用程序,即在生产中预期的相同水平,再加上设计超过峰值负载。幸运的是,前提测试生成workloads with the proper distribution of injection points. Users can't often replicate the scale of a live IoT deployment, which creates problems with IoT performance testing. If that's not practical, the best strategy is to gather data from successively larger-scale tests to plot a performance-versus-load curve. Developers should expect to run at least a half-dozen tests. After the third, they can use the results to draw a curve to predict later test results. Developers can stop testing when the curve correctly anticipates future larger-scale test results. They should run one last test at very high volume -- even if they can't actually replicate the distribution of IoT sources -- to validate the application performance beyond the design load.
应用良好的设计实践
Device testing in IoT is a problem of both test procedures and design. Most IoT pioneers have learned that if IoT applications must be customized for every new device, device introduction will be a major problem, likely riddled with errors. The key to device testing is to first design the application to abstract devices by class. That means that运动或温度传感器应向应用程序的其余部分提供一个通用接口。将每个特定设备适应该共同的抽象。这将设备测试限制在针对特定类别标准的设备测试。如果是运动传感器,它是否在适应后会显示与该课程的所有成员相同的数据?