Beruflich Dokumente
Kultur Dokumente
Volume: 3 Issue: 7
ISSN: 2321-8169
4442 - 4447
_______________________________________________________________________________________________
Load Balancing and Resource Allocation Model for SaaS Applications with
Time and Cost constraints forcloud-computing
Kalyani Ghuge1
1PG Fellow, Department of Computer Engg
G.H. Raisoni College of Engineering & Management
Pune, India
kalyani.ghuge@gmail.com
AbstractInstead of Traditional Software, nowadays we are using Cloud Computing. It enables the on-going revenue for software
providers..Advancement of Cloud Computing due to use of well established research in Web Services, networks, utility computing and
virtualization has resulted in many advantages in cost, flexibility and availability for service users. These advantages has further increased the
demand for Cloud Services, increasing both the Cloud's customer base and the scale of Cloud installations. This has resulted in many technical
issues in Service Oriented Architectures and Internet of Services (IoS) type applications such as high availability and scalability, fault tolerance.
Central to these issues is the establishment of effective load balancing techniques. In this paper focus on the load balancing and resources
provisioning approaches.Here, using the linear programming approach for dynamically allocates the resources with balancing the load.Mainly
focus on the time and cost constraints.
Keywords- Cloud Computing,LoadBalancing,Resource provisioning,Service Oriented Architecture.
__________________________________________________*****_________________________________________________
I.
INTRODUCTION
RELATED WORK
_______________________________________________________________________________________
ISSN: 2321-8169
4442 - 4447
_______________________________________________________________________________________________
nodes based on the item requirements and helps in removing
overloads on servers, switches and storage nodes.[8]
CARTON proposed a mechanism CARTON for cloud
control that unifies the use of LB and DRL. LB (Load
Balancing) is used to equally distribute the jobs to different
servers so that the associated costs can be minimized and
DRL (Distributed Rate Limiting) is used to make sure that
the resources are distributed in a way to keep a fair resource
allocation. DRL also adapts to server capacities for the
dynamic workloads so that performance levels at all servers
are equal. With very low computation and communication
overhead, this algorithm is simple and easy to implement.
Compare and Balance addressed the problem of intra-cloud
load balancing amongst physical hosts by adaptive live
migration of virtual machines. A load balancing model is
designed and implemented to reduce virtual ma-chines
migration time by shared storage, to balance load amongst
servers according to their processor or IO usage, etc. and to
keep virtual machines zero-downtime in the process.[9][10]
A distributed load balancing algorithm COMPARE AND
BAL-ANCE is also proposed that is based on sampling and
reaches equilibrium very fast. This algorithm assures that
the migration of VMs is always from high-cost physical
hosts to low-cost host but assumes that each physical host
has enough memory which is a weak assumption. To find
the reliability of the system which handle the load consider
the some factors such as Throughput used to calculate
number of task whose execution been completed in unit
time. In given scale of time throughput should be high to
improve the performance of the system.Response Time
defined as amount of time taken in distributed cloud
environment to riposte with a load balancing methodology.
The response time should be minimized for effective system
performance.[9][10] Resource Allocation algorithms for
SaaS providers minimize infrastructure cost and SLA
violations. Various algorithms are designed to check the
work of SaaS providers. Dynamic change of customers,
mapping customer requests to infrastructure level
parameters and handling heterogeneity of Virtual machines
are some of the tasks managed by the SaaS providers. Also
customers Quality of Service parameters such as response
time, and infrastructure level parameters such as service
initiation time are also considered. By taking into
consideration, the predefined SLA clauses and submitting
their QoS parameters, the customer's requests for the
enterprise software services from a SaaS provider are
considered. The requirements and the usage of the hosted
software services can be managed are accordingly changed
by the customers. The SaaS provider can use their own
infrastructure or outsourced resources from public IaaS
providers. The main objective of SaaS providers is to work
in such a way that its profit is maximized while the
customers requirements are also assured. The platform
_______________________________________________________________________________________
ISSN: 2321-8169
4442 - 4447
_______________________________________________________________________________________________
services a rate-adaptive algorithm is used. And during the
final phase it pauses the virtual machine and copies any
leftover pages to the destination and afterwards resumes the
execution there. The factors touching the total migration are
link bandwidth, migration overhead and page dirtied rate. In
the Match Making and Scheduling tells that the Match
making is the first step and scheduling is second within
the
resource
allocation
in cloud
environment.
[13]Matchmaking is that the method of allocating jobs
associated with user requests to resources designated from
the obtainable resource pool. Scheduling refers to
determining the order in which jobs mapped to a selected
resource are to be executed. It additionally tells that there
are some uncertainties that are associated with such type of
match making and scheduling
III.
SYSTEM MODEL
_______________________________________________________________________________________
ISSN: 2321-8169
4442 - 4447
_______________________________________________________________________________________________
T. The cluster log is created along with their category and is
maintained accordingly. These tables are used by the LP
solver which calculates the status of each processor with
minimum cost and time. Tasks are allotted to processors
based on the present load balancing approach. This approach
is changed when linear programming constraints changes.
B. Mathematical Model
Let S be System such that,
{P, S, Se, SDb, J, F, f, O }
S is a system that divides into the subsystem Submitters,
Processors, Functions, and Output.
P = {P1, P2 , Pn} P
_______________________________________________________________________________________
ISSN: 2321-8169
4442 - 4447
_______________________________________________________________________________________________
IV.
EXPERIMENTAL RESULTS
V.
Resource
Utilization
4
3
High
(%) 2
1
Medium
0
Cluster1
Cluster2
Cluster3
Low
CONCLUSION
_______________________________________________________________________________________
ISSN: 2321-8169
4442 - 4447
_______________________________________________________________________________________________
[12]
[13]
[14]
[15]
4447
IJRITCC | July 2015, Available @ http://www.ijritcc.org
_______________________________________________________________________________________