Abstract
Workflow has become a standard for many scientific applications that are characterized by a collection of processing elements. Particularly, a pipeline application is a type of workflow that receives a set of tasks, which must pass through all processing elements in a linear fashion. However, the strategy of using a fixed number of resources can cause under- or over-provisioning situations, besides not fitting irregular demands. In this context, our idea is to deploy the pipeline application in the cloud, so executing it with a feature that differentiates cloud from other distributed systems: resource elasticity. Thus, we propose Pipel: a reactive elasticity model that uses lower and upper load thresholds and the CPU metric to on-the-fly select the most appropriated number of compute nodes for each stage along the pipeline execution. The results were promising, presenting an average gain of 38% in the application time when comparing non-elastic and elastic executions.
Sign-in/Register to access full text options 
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Schedule a callMore From: International Journal of Computational Systems Engineering
Disclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.
