Efficient task scheduling on virtual machine in cloud computing environment

Abstract

Purpose Cloud users can access services at anytime from anywhere in the world. On average, Google now processes more than 40,000 searches every second, which is approximately 3.5 billion searches per day. The diverse and vast amounts of data are generated with the development of next-generation information technologies such as cryptocurrency, internet of things and big data. To execute such applications, it is needed to design an efficient scheduling algorithm that considers the quality of service parameters like utilization, makespan and response time. Therefore, this paper aims to propose a novel Efficient Static Task Allocation (ESTA) algorithm, which optimizes average utilization. Design/methodology/approach Cloud computing provides resources such as virtual machine, network, storage, etc. over the internet. Cloud computing follows the pay-per-use billing model. To achieve efficient task allocation, scheduling algorithm problems should be interacted and tackled through efficient task distribution on the resources. The methodology of ESTA algorithm is based on minimum completion time approach. ESTA intelligently maps the batch of independent tasks (cloudlets) on heterogeneous virtual machines and optimizes their utilization in infrastructure as a service cloud computing. Findings To evaluate the performance of ESTA, the simulation study is compared with Min-Min, load balancing strategy with migration cost, Longest job in the fastest resource-shortest job in the fastest resource, sufferage, minimum completion time (MCT), minimum execution time and opportunistic load balancing on account of makespan, utilization and response time. Originality/value The simulation result reveals that the ESTA algorithm consistently superior performs under varying of batch independent of cloudlets and the number of virtual machines’ test conditions.

A Secure and Robust Trust-Based Task Allocation Model for Batch-of-Tasks (BoT) in Cloud Computing

“…At this time, tasks can be executed, whether other tasks finish or not [29][30]. Independent task scheduling examples are MET [23,31], MCT [31], SUFFERAGE [32], MinMin [23][24], MaxMin [23][24], ESTA [22].…”

“…The traditional and security-aware task allocation architecture is proposed in related work MinMin [23][24], MaxMin [23][24], ESTA [22], MinMin(SA) [38], MaxMin(SA) [38], SPMinMin [36][37] and SPMaxMin [38]. However, these are not well integrating the security issues such as security overhead and flowtime into scheduling.…”

“…and Security-Prioritized Efficient Static Task Allocation (SP-ESTA) are proposed which integrates security demands and trust level in allocation.  This paper is an extension of our previous work Efficient Static Task Allocation (ESTA) [22].  SA-ESTA and SP-ESTA adjust themselves to the static environment which mainly includes security overhead, security demand of each cloudlet and trust level of each VMs running on the IaaS Cloud.…”

“… The proposed security-aware and prioritized methodology is incorporated to security into MinMin and MaxMin algorithms for comparison purposes namely by MinMin with security-aware (SA-MinMin), MinMin with security prioritized (SP-MinMin), MaxMin with security-aware (SA-MaxMin) and MaxMin with security prioritized (SP-MaxMin).  To estimate the performance of SA-ESTA and SP-ESTA, the experimental results are based on random testbed trace and compared with incorporated baseline algorithms such as SA-MinMin, SP-MinMin, SA-MaxMin, SP-MaxMin, MinMin [23][24], MaxMin [23][24], and ESTA [22]. The rest of the paper is structured as follows: Section 2 discusses the related work for this domain.…”

“…In order to show the working of the security-aware and security priority algorithms used in this model, a classic illustration is compiled in which a BoT with 12 independent cloudlets set β = {C1, C2, C3, C4, C5, C6, C7, C8, C9, C10, C11, C12} allocated onto the set of VMs Ṽ = {V1, V2, V3} step by step explained in section 4.5. Where cloudlets are defined as C1= (104, 6) means the length of cloudlet C1 is 104 MIs with 6 security demands while V1 =(22,7,45) means the speed of VM V1 is 22 MIPS. It can suggest security upto 7 levels and 45 is the initial ready time.…”