Unblocking parallelization: Difference between revisions
Jump to navigation
Jump to search
(new) |
mNo edit summary |
||
| Line 1: | Line 1: | ||
Unblocking parallelization is a concept in which different operations like asking for values and reading values are called in separated functions of a Device Class. That way, all devices contributing to a measurement point are first asked for their values. If one of the devices needs some more time to respond, other device can already process their queries. | Unblocking parallelization is a concept in which different operations like asking for values and reading values are called in separated functions of a Device Class. That way, all devices contributing to a measurement point are first asked for their values. If one of the devices needs some more time to respond, other device can already process their queries. | ||
Finally, all devices are read out during another function and the overall time to get all values from all devices is only limited by the device which | Finally, all devices are read out during another function and the overall time to get all values from all devices is only limited by the device which needs the longest time to respond but not by sum of the response time of all devices. | ||
Latest revision as of 23:44, 21 May 2017
Unblocking parallelization is a concept in which different operations like asking for values and reading values are called in separated functions of a Device Class. That way, all devices contributing to a measurement point are first asked for their values. If one of the devices needs some more time to respond, other device can already process their queries. Finally, all devices are read out during another function and the overall time to get all values from all devices is only limited by the device which needs the longest time to respond but not by sum of the response time of all devices.