Abstract: A provider network is configured to provide continuous workflow service for an open-ended number of workflows using non-persistent threads. The provider network includes a workflow translator service configured to receive workflows defined according to multiple workflow domain specific languages and translate the received workflows into a particular domain specific language used by the workflow service to execute workflows. In some cases, the provider network includes a workflow handling service and a workflow evaluation service. The workflow handling service may receive indications of task completion events related to respective workflows, and in turn may send non-blocking requests for workflow decisions from the workflow evaluation service. In generating a workflow decision, the workflow evaluation service may determine resources for executing a workflow.

Abstract: A user device and server automatically test the performance of a browser. For example, at the request of a user or developer, the user device retrieves and loads a set of reference pages that are used to individually measure and record the performance of the browser as one content parameter is varied and the remaining content parameters are held constant. The performance of the browser may be measured in terms of page processing time. Based on the measured page processing times, the server may determine a relationship between each parameter and a page processing time. The server then develops a model for estimating the page load time of an actual page using the determined relationships. To estimate the page load time of an actual page, the server determines values for the content parameters associated with the actual page and applies those values to the developed model.

Abstract: A provider network for providing continuous workflow service for an open-ended number of workflows using non-persistent threads. In some cases, the provider network includes a workflow handling service and a workflow evaluation service. The workflow handling service may receive indications of task completion events related to respective workflows, and in turn may send non-blocking requests for workflow decisions from the workflow evaluation service. In generating a workflow decision, the workflow evaluation service may determine resources for executing a workflow evaluation thread for generating the workflow decision. Further, a given workflow evaluation thread may determine a workflow decision without relying on a previously stored state for a state machine corresponding to the workflow. In this way, a given workflow decision may be determined on different allocated resources at different points in time in maintaining the workflow.

Abstract: A workflow interpreter service that interprets a workflow definition language for specifying a workflow definition. Further, the workflow definition language provides features for maintaining control over data flows for data that is passed from one state to another among states of a state machine for a workflow and features for handling errors that may occur within any given state of a workflow state machine. Such control over data flow in between states allows for a given workflow to be processed incrementally, and among multiple different computing resources. Further, the workflow definition language error handling features provide for robust error handling within the state machine framework corresponding to workflow.

Abstract: A workflow interpreter service that interprets a workflow definition language for specifying a workflow definition. Further, the workflow definition language provides features for maintaining control over data flows for data that is passed from one state to another among states of a state machine for a workflow. Such control over data flow in between states allows for a given workflow to be processed incrementally, and among multiple different computing resources.

Abstract: A provider network for providing continuous workflow service for an open-ended number of workflows using non-persistent threads. In some cases, the provider network includes a workflow handling service and a workflow evaluation service. The workflow handling service may receive indications of task completion events related to respective workflows, and in turn may send non-blocking requests for workflow decisions from the workflow evaluation service. In generating a workflow decision, the workflow evaluation service may determine resources for executing a workflow evaluation thread for generating the workflow decision. Further, a given workflow evaluation thread may determine a workflow decision without relying on a previously stored state for a state machine corresponding to the workflow. In this way, a given workflow decision may be determined on different allocated resources at different points in time in maintaining the workflow.