| Literature DB >> 32310989 |
R Swathy1, B Vinayagasundaram1, G Rajesh2, Anand Nayyar3, Mohamed Abouhawwash4,5, Mohamed Abu Elsoud6,7.
Abstract
On-demand cloud computing is one of the rapidly evolving technologies that is being widely used in the industries now. With the increase in IoT devices and real-time business analytics requirements, enterprises that ought to scale up and scale down their services have started coming towards on-demand cloud computing service providers. In a cloud data center, a high volume of continuous incoming task requests to physical hosts makes an imbalance in the cloud data center load. Most existing works balance the load by optimizing the algorithm in selecting the optimal host and achieves instantaneous load balancing but with execution inefficiency for tasks when carried out in the long run. Considering the long-term perspective of load balancing, the research paper proposes Stackelberg (leader-follower) game-theoretical model reinforced with the satisfaction factor for selecting the optimal physical host for deploying the tasks arriving at the data center in a balanced way. Stackelberg Game Theoretical Model for Load Balancing (SGMLB) algorithm deploys the tasks on the host in the data center by considering the utilization factor of every individual host, which helps in achieving high resource utilization on an average of 60%. Experimental results show that the Stackelberg equilibrium incorporated with a satisfaction index has been very useful in balancing the loading across the cluster by choosing the optimal hosts. The results show better execution efficiency in terms of the reduced number of task failures by 47%, decreased 'makespan' value by 17%, increased throughput by 6%, and a decreased front-end error rate as compared to the traditional random allocation algorithms and flow-shop scheduling algorithm.Entities:
Year: 2020 PMID: 32310989 PMCID: PMC7170225 DOI: 10.1371/journal.pone.0231708
Source DB: PubMed Journal: PLoS One ISSN: 1932-6203 Impact factor: 3.240
Fig 1Stackelberg load balancer’s architecture diagram.
Fig 2Flow diagram of SGMLB.
Fig 3Makespan analysis.
Makespan values in seconds for different task requests.
| Makespan (in Seconds) | |||
|---|---|---|---|
| Task Requests | SGMLB | Flow Shop | Random Allocation |
| 200 | 2820 | 3200 | 3520 |
| 400 | 3020 | 3650 | 3930 |
| 600 | 3625 | 4045 | 4325 |
| 800 | 4300 | 4950 | 5615 |
| 1000 | 5330 | 6050 | 6555 |
Number of tasks failed against total tasks submitted.
| Failed No of Tasks | |||
|---|---|---|---|
| Total Tasks | SGMLB | Flow Shop | Random Allocation |
| 200 | 45 | 53 | 68 |
| 400 | 66 | 78 | 138 |
| 600 | 83 | 165 | 236 |
| 800 | 112 | 245 | 356 |
| 1000 | 146 | 293 | 418 |
Fig 4Failed number of tasks analysis.
Throughput value for task requests per second.
| Throughput (Requests/Second) | |||
|---|---|---|---|
| Task Requests | SGMLB | Flow Shop | Random Allocation |
| 200 | 0.5 | 0.9 | 1.5 |
| 400 | 1.2 | 1.6 | 1.5 |
| 600 | 1.7 | 1.8 | 1.4 |
| 800 | 2.2 | 1.8 | 1.35 |
| 1000 | 2.9 | 2.3 | 1.5 |
Fig 5Throughput analysis.
Resource utilization in every iteration.
| Resource Utilization | |||
|---|---|---|---|
| Iteration | SGMLB | Flow Shop | Random Allocation |
| Iteration01 | 50 | 45 | 30 |
| Iteration02 | 107 | 87 | 43 |
| Iteration03 | 198 | 126 | 56 |
| Iteration04 | 257 | 183 | 72 |
| Iteration05 | 365 | 232 | 150 |
Fig 6Resource utilization analysis.
Front-end error rate.
| Time (Sec) | Total Request | Front-end Error Rate % | ||
|---|---|---|---|---|
| SGMLB | Random | Flow-Shop | ||
| 1800 | 1261 | 2 | 3 | 2.7 |
| 3600 | 2356 | 2.5 | 3.5 | 2.3 |
| 5400 | 5124 | 4 | 6 | 4.1 |
| 7200 | 9982 | 5.7 | 7.3 | 5.7 |
| 9000 | 21395 | 8 | 8.1 | 8.4 |
Fig 7Front-end error rate analysis.
Price strategy for the hosts based on available load.
| Load Capacity | Price ($) |
|---|---|
| 40 | 0.83 |
| 65 | 0.45 |
| 82 | 0.27 |
| 98 | 0.14 |
| 110 | 0.07 |
Fig 8Price value computed for load capacity.