The Custom Device readme.md file contains a paragraph: "CPU Performances".
It would be very valuable to users to have other tests showing how much Asynchronous part execution time varies when playing with data handled by Asynchronous part. It would also help for Issue #3 as a reference.
In a real context, we can imagine that users won't play that often with Start/Stop commands channels and invoke them repeatedly. But, we can imagine that, often, users will update Words data from frames and also trigger "Acyclic" frames.
At least 2 tests could be done to characterize CPU impact when:
There are an update of 10%, 50% and 100% (so 3 variants) of the Words from frame at each iteration.
There is a trigger of Acyclic messages, do the test for one message and more messages (how much is to be defined). In the end, we want to know how CD behaves and whether execution duration is linear with number of messages...
The Custom Device readme.md file contains a paragraph: "CPU Performances".
It would be very valuable to users to have other tests showing how much Asynchronous part execution time varies when playing with data handled by Asynchronous part. It would also help for Issue #3 as a reference.
In a real context, we can imagine that users won't play that often with Start/Stop commands channels and invoke them repeatedly. But, we can imagine that, often, users will update Words data from frames and also trigger "Acyclic" frames.
At least 2 tests could be done to characterize CPU impact when:
There are an update of 10%, 50% and 100% (so 3 variants) of the Words from frame at each iteration.
There is a trigger of Acyclic messages, do the test for one message and more messages (how much is to be defined). In the end, we want to know how CD behaves and whether execution duration is linear with number of messages...