International IRATJ

Robotics & Automation Journal
Research Article
Volume 1 Issue 1 - 2016
A Multi-Agent based Load balancing System in IaaS Cloud Environment
Sina Keshvadi1* and Behnam Faghih2
1Department of IT, Payame Noor University (PNU), Iran
2Department of Technical and Vocational University, Iran
Received: August 27, 2016 | Published: October 04, 2016
*Corresponding author: Sina Keshvadi, Department of IT, Payame Noor University (PNU), Tehran, Iran, Email:
Citation: Keshvadi S, Faghih B (2016) A Multi-Agent based Load balancing System in IaaS Cloud Environment. Int Rob Auto J 1(1): 00002. DOI: 10.15406/iratj.2016.01.00002

Abstract

Infrastructure as a service (IaaS) is a type of cloud computing in which a third-party provider hosts virtualized computing resources over the Internet for executing tasks in the cloud computing. Whenever some VMs are overloaded and some VMs are under loaded, this situation may cause to SLA violation and leads to the reduction of customer satisfaction level and further affects the cloud provider leading to penalty. However, in this study, we propose a Multiple Agent-based Load Balancing Algorithm (MA) in which shift the load in the IaaS to achieve well dynamic load balancing across virtual machines for maximizing the utilization. The proposed algorithm with regard to changing environment and characteristics of the VMs, perform both of sender-initiated and receiver-initiated approach to balances the load of an IaaS in such a way that the amount of waiting time of the tasks in the queue is minimal and at the same time the SLA is guaranteed. We have compared the proposed algorithm with existing load balancing and scheduling algorithms via simulation. The simulation results show that the proposed algorithm is more effective and there is a good improvement in the load-balance, response time and makespan.

Keywords: Cloud computing; Load balancing; Scheduling; Mobile agents

Abbreviations

IAAS: Infrastructure as Service; VMM: Virtual Machine Monitor; PAAS: Platform As A Service; SAAS: Software As A Service; VMS: Virtual Machines

Introduction

As defined by NIST, Cloud Computing is “a model for enabling ubiquitous, convenient, on-demand network access to a shared pool of configurable computing resources (e.g, networks, servers, storage applications and services) that can be rapidly provisioned and released with minimal management effort or service provider interaction”. Cloud Computing is a broad term that describes a broad range of services. In these systems, resources are provided as service on-demand. The services provided by cloud computing are infrastructure as a service (IaaS), platform as a service (PaaS) and software as a service (SaaS) that are made available as pay-as-you-go model to subscribers, and it guarantees to them that it sticks to the Service Level Agreement (SLA). IaaS usage allows the enterprise IT or web operations group to install and build their application environments on infrastructure without the pain of purchasing, installing and ongoing maintenance of the infrastructure [1].

 Moreover, day by day subscribers’ requires are rising for computing resources and their needs have dynamic heterogeneity and platform irrelevance in IaaS. This make datacenters expensive to maintain which is accompany with wasted energy and floor space, low resource utilization, and significant management overhead [2]. The virtualization technology come into sight, provides cloud datacenters have become more flexible, more secure, and provide better support for on-demand allocation and it address the issue of heterogeneity and platform irrelevance in a better way, and at the same time the SLA is guaranteed. With IaaS, the physical infrastructure of IT systems is typically moved offsite and a service provider grants access to a virtualized environment of computing resources to its customers. In these systems, cloud datacenters should have ability to migrate an application from one set of resources to another in a non-disruptive manner. Such agility becomes a key in modern cloud computing infrastructures that aim to efficiently share and manage extremely large data centers [2].

The processing units in cloud virtualization environments are called as virtual machines (VMs) [3]. In order to improve resource utility, resources must be properly allocated and load balancing must be guaranteed. Load balancing aims to optimize resource use, maximize throughput, minimize response time, and avoid overload or sitting idle of any single resource. Therefore, how to schedule VM resources to realize load balancing in cloud computing and to improve resource utility becomes an important research point. In this case, it is the responsibility for the scheduler to balance the loads across the machines in IaaS. In the absence of load balancing provision, efficiency of some overloaded virtual machines can sharply degrade at times, leading to violation of SLA [4]. The violation of the SLA is a major aspect of IaaS and the violation leads to the reduction of customer satisfaction level and further affects the cloud provider leading to penalty.

According to the whole information of each VM in an IaaS, the performance will be managed and enhanced. There are several methods can monitor and collect the relevant information of node that includes broadcasting, the centralized polling and agent [5]. The agent mechanism is used to collect the related node information to achieve efficient utilization resource and enhance work efficiency. It has inherent navigational autonomy and it could collect related information of each VM, such as CPU utilization, remaining CPU capability, remaining memory, transmission rate, etc. However, in this study, multiple agents are used to gather the related information in IaaS environment and reduce the resources wasting and cost. We proposed a load balancing algorithm in cloud IaaS environment by using agents that also the distinctive characteristics of virtual machines are considered.

The rest of this paper is organized as follows:

  1. A review of the related work is discussed in Section.
  2.  The proposed algorithm is detailed in Section.
  3.  Section.
  4. Describes the simulation setup and the results. Finally, Section.
  5.  Concludes this study.

Related Work

There are basically two kinds of load balancing techniques: static and dynamic [6]. Static algorithms are mostly suitable for homogeneous and stable environments and can produce very good results in these environments. However, they are usually not flexible and cannot match the dynamic changes to the attributes during the execution time. In the static approach, the task allocation does not change during execution while in the dynamic it does. A good comparison of these techniques is mentioned in [7]. Dynamic load balancing algorithms are advantageous over static algorithms. But to gain this advantage, we need to consider the additional cost associated with collection and maintenance of the load information.

A dynamic load balancing algorithm has three main components [6]. The information, transfer, and location strategies. Information strategy is responsible for collecting information about nodes in the system. Transfer strategy selects a job for transfer from a local node to a remote node. Location strategy selects a destination node for a transferred task. Two main issues concerning load balancing activity that depend on the transfer strategy employed are: when is the right time to start it and what jobs are subjected to it. Two approaches are commonly used to start the load balancing activity: the time a new job arrives or is created at a node and the time a finished job departs from a node. Algorithms which make load balancing decisions at the arrival or creation of a new job are referred to as sender-initiated, while algorithms which make load balancing decisions at the departure of a finished job are referred to as receiver-initiated [6].

[8]. Discusses the different qualitative metrics or parameters like performance, scalability, associated overhead etc [2]. Introduces online load balance scheduling for Cloud data centers. They propose an online resource scheduling algorithm (OLRSA), which considers real-time and multidimensional resource scheduling. Then Lowest Integrated-load First Algorithm (LIF) is also introduced [4]. Proposes an Autonomous Agent-Based Load Balancing Algorithm (A2LB) which provides dynamic load balancing for cloud environment by using agents. They introduced a fitness value metric in which the fitness values give the status of a virtual machine.

As cloud task scheduling is an NP-hard optimization problem [9]. Recently numerous nature inspired models have received a lot of research attentions. A good task scheduler should adapt its scheduling strategy to the changing environment and the types of tasks Hu et al. [10]. Proposed genetic algorithm based scheduling mechanism for load balancing among virtual machines Xu et al. [11]. Introduced a model for load balancing in the public cloud by using game theory [12]. Proposed a load balancing technique for cloud computing environments based on the behaviour of honey bee foraging strategy. The tasks removed from these VMs are treated as honey bees, which are the information updaters globally. Their work also considers the priorities of the tasks. Load Balancing can also be classified in centralized and distributed load balancing or in application-level and system-level load balancing. In the next part, we propose our mechanism to load balance in cloud IaaS datacenters.

Proposed Algorithm

Whenever a VM becomes overloaded, the service provider has to distribute the load in such a manner that the available resources will be utilized in a proper manner and load at all the virtual machines will remain balanced. Identifying when it is best to migrate an application in an overloaded virtual machine to another place has a direct impact on resource utilization. This issue can be best achieved by an efficiently monitoring the utilization of computing resources. Agent is an autonomous unit, which is capable of performing specified tasks on their own. In follow, we introduce our agents.

Agents

Our proposed mechanism comprises of three agents: Virtual Machine Monitor (VMM) Agent, Datacenter Monitor (DCM) Agent and Negotiator Ant (NA) Agent. VMM and DCM agents are generally agents whereas NA agent is an ant, which is a special category of mobile agents. Since load balancing in IaaS cloud computing systems would require searching for under loaded servers and resources, ant agents suit the purpose and fulfil it appropriately without putting additional burden on network.

  1. VM Monitor Agent (VMM Agent)

To enhance the monitoring services, each virtual machine in IaaS is supported with a Virtual machine Monitor agent that we call it VMM Agent. VMM collects the CPU, memory and bandwidth utilization of individual virtual machine hosted with different types of tasks to monitor the load. This agent is supported with a table named as VMLocal_Table as below (Table 1). VMLocal_Table store the state of a vm. Where Load Status is categorized in under loaded, normal and overloaded statuses. Each VMM agent uses its VMLocal_Table to monitor its load periodically and determines the load status.

VM ID

RAM

CPU

BW

OS

Load Status

VM1

µ1

λ1

γ1

Type 1

Status VM1

VM2

µ2

λ2

γ2

Type 2

Status VM2

VMn

µn

λn

γn

Type n

Status VMn

Table 1: VMLocal_table store the state of a vm.

Load of a VM can be calculated as follow [r13]:

Load ( % ) =  CP U μ  + ME M μ  + NE T μ 3 ×100 MathType@MTEF@5@5@+= feaagKart1ev2aaatCvAUfeBSjuyZL2yd9gzLbvyNv2CaerbuLwBLn hiov2DGi1BTfMBaeXatLxBI9gBaerbd9wDYLwzYbItLDharqqtubsr 4rNCHbGeaGqiVu0Je9sqqrpepC0xbbL8F4rqqrFfpeea0xe9Lq=Jc9 vqaqpepm0xbba9pwe9Q8fs0=yqaqpepae9pg0FirpepeKkFr0xfr=x fr=xb9adbaqaaeGaciGaaiaabeqaamaabaabaaGcbaqcfaOaamitai aad+gacaWGHbGaamizaabaaaaaaaaapeGaaiiOamaabmaabaGaaiyj aaGaayjkaiaawMcaaiaacckacqGH9aqpcaGGGcWaaSaaaeaajugibi aadoeacaWGqbGaamyvaKqbaoaaBaaabaqcLbmacqaH8oqBaKqbagqa aiaacckacqGHRaWkcaGGGcGaamytaiaadweacaWGnbWaaSbaaeaaju gWaiabeY7aTbqcfayabaGaaiiOaiabgUcaRiaacckacaWGobGaamyr aiaadsfadaWgaaqaaKqzadGaeqiVd0gajuaGbeaaaeaacaaIZaaaai abgEna0kaaigdacaaIWaGaaGimaaaa@5F74@ (1)

Where CP U μ MathType@MTEF@5@5@+= feaagKart1ev2aaatCvAUfeBSjuyZL2yd9gzLbvyNv2CaerbuLwBLn hiov2DGi1BTfMBaeXatLxBI9gBaerbd9wDYLwzYbItLDharqqtubsr 4rNCHbGeaGqiVu0Je9sqqrpepC0xbbL8F4rqqrFfpeea0xe9Lq=Jc9 vqaqpepm0xbba9pwe9Q8fs0=yqaqpepae9pg0FirpepeKkFr0xfr=x fr=xb9adbaqaaeGaciGaaiaabeqaamaabaabaaGcbaqcfaOaam4qai aadcfacaWGvbWaaSbaaeaajugWaiabeY7aTbqcfayabaaaaa@3C8E@ , ME M μ MathType@MTEF@5@5@+= feaagKart1ev2aaatCvAUfeBSjuyZL2yd9gzLbvyNv2CaerbuLwBLn hiov2DGi1BTfMBaeXatLxBI9gBaerbd9wDYLwzYbItLDharqqtubsr 4rNCHbGeaGqiVu0Je9sqqrpepC0xbbL8F4rqqrFfpeea0xe9Lq=Jc9 vqaqpepm0xbba9pwe9Q8fs0=yqaqpepae9pg0FirpepeKkFr0xfr=x fr=xb9adbaqaaeGaciGaaiaabeqaamaabaabaaGcbaqcfaOaamytai aadweacaWGnbWaaSbaaeaajugWaiabeY7aTbqcfayabaaaaa@3C85@ , NE T μ MathType@MTEF@5@5@+= feaagKart1ev2aaatCvAUfeBSjuyZL2yd9gzLbvyNv2CaerbuLwBLn hiov2DGi1BTfMBaeXatLxBI9gBaerbd9wDYLwzYbItLDharqqtubsr 4rNCHbGeaGqiVu0Je9sqqrpepC0xbbL8F4rqqrFfpeea0xe9Lq=Jc9 vqaqpepm0xbba9pwe9Q8fs0=yqaqpepae9pg0FirpepeKkFr0xfr=x fr=xb9adbaqaaeGaciGaaiaabeqaamaabaabaaGcbaaeaaaaaaaaa8 qacaWGobGaamyraiaadsfapaWaaSbaaSqaamaaBaaameaacqaH8oqB aeqaaaWcbeaaaaa@3AB5@ are average utilization of CPU, memory, network bandwidth during each observed period, respectively. VMM agents use eq. 1 to determine the load of associated virtual machine.

  1. Datacenter Monitor Agent (DcM Agent)

This agent monitors all VMM agents in a datacenter. Actually, it performs information policy in a datacenter by monitoring the VMM’s information. This agent is supported with table termed as DcMonitor_table. This table maintains all information about status and characteristics of all virtual machines in a datacenter. It categorizes VMs based on their characteristics. A simple template of a DcMonitor_table is shown as below (Table 2).

Status

Under-Loaded; Balanced; Over Loaded

List of VMs

OS

OS Type 1; OS type 2; OS Type n

List of VMs

Number of PE

Number 1; Number 2; Number p

List of VMs

Ram

Ram Type 1; Ram type 2; Ram Type m

List of VMs

CPU

Type 1 GHz; type 2 GHz; Type m GHz

 

Bandwidth

Type 1 M; Type 2 M; Type m M;

 

Table 2: DcMonitor_table keeps the information about vms.

  1. Negotiator Ant Agent (NA)

These agents are initiated by DCM agents. It will move to other datacenters and communicate with DCM agent of that datacenter to enquire the status of VMs present there, looking for the desired configuration. On receiving the required information, it communicates the same to its parent DCM agent. Afterwards, it will stay at destination location, waiting for self-destroy message from parent. The status of the NA agent may be alive or destroyed.

MA Load Balancing Algorithm Scenario

(Figure 1) Provides high level view of proposed mechanism we should first be aware of the load status of any VM. VMM agents determine own VM’s state based on its load by eq. 1. There are overloaded, under loaded and balanced states. If the load of a VM is more than the upper threshold (s) then the system is overloaded. If the load is less than a lower threshold (ν), the system is under loaded. Otherwise the system is in a balanced state. In the overloaded state a heavily loaded vm is the one who initiates load balancing. Hence, this implies that this strategy is coupled with a sender-initiated transfer strategy. In the under loaded state a lightly loaded vm is the one who initiates load balancing. Hence, this implies that this strategy is coupled with a receiver-initiated transfer strategy (Figure 1). MA load balancing scenario after finding the state of a vm as overloaded, VMM send a load balancing request to its DCM agent. DCM look ups its DcMonitor_table to find an under loaded VM with desired configuration. If found, the task moved from overloaded VM to under loaded VM to perform. If not, DCM agent initiates some NA agents per each datacenter in the system to communicate with other datacenters. The NAs go straightforward to the given datacenter and request the desired VM from their DCM agents. If not found, NA send back an unsuccessful TTL-based message to its parent and wait for destroy message. In the case that the desired VM found, the characteristics of the VM send back to its DCM agent and wait for parent message.

Figure1: MA load balancing scenario.

In the other hands, DCM agent receives reports from its NAs. If DCM agent don’t receive message, resend another NA agent to the datacenter. Then, it sends destroy message to any NA which couldn’t found a desired VM. If all received message are negative, send a negative reply to requested VM in which the load balancing is not feasible. Otherwise, it select the appropriated VM from all received options based on the load and response time and send a transfer message to that NA and a destroy message to all other ants. Now, it transfers task from requested VM to given VM and after receive new load status, DCM agent will update the DcMonitor_table. Algorithms of various agents deployed in proposed framework are given as follow (Figure 2). VMM, DCM and NA Agents algorithms.

Figure 2:  VMM, DCM and NA Agents algorithms.

Simulation Result

In this section, we will show simulation results for our proposed algorithm i.e. MA load balancing algorithm compared with other existing algorithms. Experimenting new techniques or strategies in repeatable, dependable, and scalable environments using real-world Cloud environments is not practically possible as such experiments will compromise the end users Qos requirements like security, cost, and speed. There is a need for a good simulator for experimental purposes. One such a simulator is CloudSim [14,15]. This simulator is a generalized simulation framework that allows modeling, simulation and experimenting the cloud computing infrastructure and application services. We have extended the classes of CloudSim simulator to simulate our algorithm. Our agents are implemented using java programming. All simulations are collected using a core-i3 pc with 2.4 GHz CPU and 4 GB memory. We compare the simulation results of our proposed algorithm with different low and over loaded ratios with these existing algorithms:

  1. First In First out (FIFO): a general scheduling algorithm that implements Fisrt-In-First-Out policy to allocate the VM requests to the PM that can provide the resource required.
  2. Weighted Round Robin (WRR): a common routing policy offered in cloud load balancers, which allocates the task to each VM in a sequentially turn.
  3. List Scheduling algorithm (LS): a generic greedy algorithm. Whenever a machine becomes available, process any unprocessed job.

Measurement parameters

In this paper we study three parameters: makespan, response time and, degree of imbalance. These parameters are used to evaluate the effect of load balancing approach. In the following, we introduce them briefly and then we study the impact of algorithms on these parameters. Makespan. Makespan can be defined as the overall task completion time. We denote completion time of task Ti on VMj as CTij. Hence, the makespan is defined as the following function [12]:

makespan = max{C T ij  iΕ T , i = 1, 2, ... , n and jΕ VM,j = 1,2, ... , m} (2) MathType@MTEF@5@5@+= feaagKart1ev2aaatCvAUfeBSjuyZL2yd9gzLbvyNv2CaerbuLwBLn hiov2DGi1BTfMBaeXatLxBI9gBaerbd9wDYLwzYbItLDharqqtubsr 4rNCHbGeaGqiVu0Je9sqqrpepC0xbbL8F4rqqrFfpeea0xe9Lq=Jc9 vqaqpepm0xbba9pwe9Q8fs0=yqaqpepae9pg0FirpepeKkFr0xfr=x fr=xb9adbaqaaeGaciGaaiaabeqaamaabaabaaGcbaqcfaieaaaaaa aaa8qacaWGTbGaamyyaiaadUgacaWGLbGaam4CaiaadchacaWGHbGa amOBaiaacckacqGH9aqpcaGGGcGaciyBaiaacggacaGG4bGaai4Eai aadoeacaWGubWaaSbaaeaacaWGPbGaamOAaaqabaGaaiiOaiaacMga cqqHvoqrcaGGGcGaamivaiaacckacaGGSaGaaiiOaiaadMgacaGGGc Gaeyypa0JaaiiOaiaaigdacaGGSaGaaiiOaiaaikdacaGGSaGaaiiO aiaac6cacaGGUaGaaiOlaiaacckacaGGSaGaaiiOaiaad6gacaGGGc Gaamyyaiaad6gacaWGKbGaaiiOaiaadQgacqqHvoqrcaGGGcGaamOv aiaad2eacaGGSaGaamOAaiaacckacqGH9aqpcaGGGcGaaGymaiaacY cacaaIYaGaaiilaiaacckacaGGUaGaaiOlaiaac6cacaGGGcGaaiil aiaacckacaWGTbGaaiyFaiaacckacaGGOaGaaGOmaiaacMcaaaa@7DFA@

Response time. Response time is the amount of time taken between submission of a request and the first response that is produced. The reduction in waiting time is helpful in improving responsiveness of the VMs.

Degree of imbalance. Imbalance can be calculated as standard deviation of the load:

σ =  1 m i=1 m (P T i  PT ) 2 MathType@MTEF@5@5@+= feaagKart1ev2aaatCvAUfeBSjuyZL2yd9gzLbvyNv2CaerbuLwBLn hiov2DGi1BTfMBaeXatLxBI9gBaerbd9wDYLwzYbItLDharqqtubsr 4rNCHbGeaGqiVu0Je9sqqrpepC0xbbL8F4rqqrFfpeea0xe9Lq=Jc9 vqaqpepm0xbba9pwe9Q8fs0=yqaqpepae9pg0FirpepeKkFr0xfr=x fr=xb9adbaqaaeGaciGaaiaabeqaamaabaabaaGcbaqcfaOaeq4Wdm heaaaaaaaaa8qacaGGGcGaeyypa0JaaiiOamaakaaabaWaaSaaaeaa caaIXaaabaGaamyBaaaaaeqaamaaqahabaGaaiikaiaadcfacaWGub WaaSbaaeaacaWGPbaabeaaaeaacaWGPbGaeyypa0JaaGymaaqaaiaa d2gaaiabggHiLdGaaiiOaiabgkHiTiaadcfacaWGubGaaiykamaaCa aabeqaaiaaikdaaaaaaa@4C00@

Where PT i is processing time of VMi:

(PT i) = load v  M i Capacit y i MathType@MTEF@5@5@+= feaagKart1ev2aaatCvAUfeBSjuyZL2yd9gzLbvyNv2CaerbuLwBLn hiov2DGi1BTfMBaeXatLxBI9gBaerbd9wDYLwzYbItLDharqqtubsr 4rNCHbGeaGqiVu0Je9sqqrpepC0xbbL8F4rqqrFfpeea0xe9Lq=Jc9 vqaqpepm0xbba9pwe9Q8fs0=yqaqpepae9pg0FirpepeKkFr0xfr=x fr=xb9adbaqaaeGaciGaaiaabeqaamaabaabaaGcbaqcfaieaaaaaa aaa8qadaWcaaqaaiaadYgacaWGVbGaamyyaiaadsgacaGGGcGaamOD aiaacckacaWGnbWaaSbaaeaacaWGPbaabeaaaeaacaWGdbGaamyyai aadchacaWGHbGaam4yaiaadMgacaWG0bGaamyEamaaBaaabaGaamyA aaqabaaaaaaa@47F1@

Make span

Figure 3 illustrates the comparison of makespan between MA, FIFO, WRR and LS Algorithms. The X-axis represents number of tasks and the Y-axis represents the Makespan. MA is more efficient and has a lower Makespan when compared with other three algorithms.

Figure 3: Comparison of makespan.

Response time

Figure 4 illustrates the response time of VMs in seconds for MA, FIFO, WRR and LS Algorithms. The X-axis represents number of tasks and the Y-axis represents time in seconds. It is evident that MA is more efficient compared with other three methods.

Figure 4: Comparison of Response Time.

Degree of imbalance

Figure 5 shows the comparison of degree of imbalance between MA, Random, WRR and LS Algorithms. The X-axis represents number of tasks and the Y-axis represents the degree of imbalance. It is clearly evident that by load balancing with MA, the degree of imbalance is greatly reduced.

Figure 5: Comparison of degree of imabalance.

References

  1. A Meeraa, S Swamynathan (2013) Agent based Resource Monitoring System in IaaS Cloud Environment. International Conference on Computational Intelligence: Modeling Techniques and Applications (CIMTA) 10: 200-207.
  2. WH Tian, Y Zhao, YL Zhong, MX Xu, C Jing (2011) Dynamic and integrated load-balancing scheduling algorithms for Cloud data centers. Cloud Computing and Intelligence Systems (CCIS) 8(6): 117-126.
  3. Y Ding, X Qin, L Liu, T Wang (2015) Energy efficient scheduling of virtual machines in cloud with deadline constraint. Quality of Service in Grid and Cloud Netherlands 50(c): 62-74.
  4. Singha A, Junejab D, Malhotra M (2015) Autonomous Agent Based Load Balancing Algorithm in Cloud Computing. International Conference on Advanced Computing Technologies and Applications India 45: 832-841.
  5. Wang SC, Yan KQ, Liao WP, Wang SS (2010) Towards a load balancing in a three-level cloud computing network. in proc. 3rd International Conference on. Computer Science and Information Technology (ICCSIT) 1: 108-113.
  6. A M Alakeel (2010) A Guide to dynamic Load balancing in Distributed Computer Systems. International Journal of Computer Science and Network Security (IJCSNS) 10(6): 153-160.
  7. Janhavi AB, Surve SK, S Prabhu (2010) Comparison of Load Balancing Algorithms in a Grid. Data Storage and Data Engineering (DSDE), International Conference 20-23.
  8. Sreenivas V, Pratha M, Kemal M (2014) Load balancing techniques: Major challenge in Cloud Computing - a systematic review. Electronics and Communication Systems (ICECS), International Conference, Africa, pp. 1-6.
  9. Tawfeek MA, El Sisi A, Keshk AE, Torkey FA (2013) Cloud task scheduling based on ant colony optimization. Computer Engineering & Systems (ICCES), 8th International Conference, Egypt, p. 64-69.
  10. J Hu, J Gu, G Sun, T Zhao (2010) A Scheduling Strategy on Load Balancing of Virtual Machine Resources in Cloud Computing Environment. Proc PAAP p. 89-96.
  11. M Moradi, MA Dezfuli, MH Safavi (2010) A New Time Optimizing Probabilistic Load Balancing Algorithm in Grid Computing IEEE, Iran.
  12. Dhinesh Babu LD, Krishna PV (2013) Honey bee behavior inspired load balancing of tasks in cloud computing environments. Applied Soft Computing 13(5): 2292-2303.
  13. Wood T, Prashant S, Arun V, Mazin Y (2007) Black-box and Gray-box Strategies for Virtual Machine Migration in the proceedings of Symp. On Networked Systems Design and Implementation (NSDI) Portland, USA, pp.1-14.
  14. RN Calheiros, R Ranjan, A Beloglazov, CAF De Rose, Rajkumar B (2011) CloudSim: a toolkit for modeling and simulation of cloud computing environments and evaluation of resource provisioning algorithms. Software: Softw Pract Exper 41(1): 23-50.
  15. R Buyya, R Ranjan, RN Calheiros (2009) Modeling simulation of scalable cloud computing environments and the cloudsim toolkit: challenges and opportunities. Australia, p. 21-24.
© 2014-2016 MedCrave Group, All rights reserved. No part of this content may be reproduced or transmitted in any form or by any means as per the standard guidelines of fair use.
Creative Commons License Open Access by MedCrave Group is licensed under a Creative Commons Attribution 4.0 International License.
Based on a work at http://medcraveonline.com
Best viewed in Mozilla Firefox | Google Chrome | Above IE 7.0 version | Opera |Privacy Policy