The DE then provides the means to build the flow into an action that can be invoked within OpenWhisk. A Jenkins pipeline is executed, and as a result, the engineer comes up with a new action from their flow.
The deployed actions are then tested via flows dedicated to invoking deployed actions. The outputs of the deployed actions are compared to those of the local flows.
Finally, deployed actions can be evaluated under different scenarios implemented using dedicated load generator nodes.
The results of such tests can be as follows, where experiments last 2 minutes continuous requests, each request arriving at a fixed delay after the previous. As long as the delays are larger than the inference time, the achieved rate follows the increase of that of a system with infinite resources. When the delay drops below the execution time, then the achieved rate reaches a plateau. Even more frequent requests push Openwhisk beyond the accepted maximum request level, dropping the requests, resulting to a performance collapse.