2022
DOI: 10.4018/ijghpc.301587
|View full text |Cite
|
Sign up to set email alerts
|

A QoS-Enabled Load Balancing Approach for Cloud Computing Environment Join Minimum Loaded Queue (JMLQ)

Abstract: Cloud computing delivers the on-demand virtualized resources to its consumer for servicing their request on a metered basis. During the high demand of cloud resources the load on system increases that may unbalance the system which affects the quality of service parameters (QoS) adversely that leads to violations of service level agreement (SLA). Role of load balancing is significant in such an environment as it enhances the distribution of workload across multiple devices for example across network links, a c… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1

Citation Types

0
10
0

Year Published

2022
2022
2023
2023

Publication Types

Select...
2
1

Relationship

0
3

Authors

Journals

citations
Cited by 3 publications
(10 citation statements)
references
References 20 publications
0
10
0
Order By: Relevance
“…The incoming task probes the first dispatcher I-queue with ID 0 having identification D 0 to get a minimum loaded VM; If it finds VMs within I-queue, the task is mapped to the first minimum loaded VM, and it is removed from the corresponding I-queue. On the other side, if the attached I-queue is empty, the task is directed toward the adjacent dispatcher I-queue to get a minimum loaded VM. VM mapping to I-queues: EQoS-enabled JMLQ uses the d-limit concept of our previous proposed approach JMLQ (Sharma et al , 2019c, 2021) to set an upper bound for the number of VMs to be placed in an I-queue. After completion of the task, the VM is directed toward the beginning dispatcher’s I-queue for joining it.…”
Section: Enhanced Quality Of Service-enabled Join Minimum Loaded Queu...mentioning
confidence: 99%
See 4 more Smart Citations
“…The incoming task probes the first dispatcher I-queue with ID 0 having identification D 0 to get a minimum loaded VM; If it finds VMs within I-queue, the task is mapped to the first minimum loaded VM, and it is removed from the corresponding I-queue. On the other side, if the attached I-queue is empty, the task is directed toward the adjacent dispatcher I-queue to get a minimum loaded VM. VM mapping to I-queues: EQoS-enabled JMLQ uses the d-limit concept of our previous proposed approach JMLQ (Sharma et al , 2019c, 2021) to set an upper bound for the number of VMs to be placed in an I-queue. After completion of the task, the VM is directed toward the beginning dispatcher’s I-queue for joining it.…”
Section: Enhanced Quality Of Service-enabled Join Minimum Loaded Queu...mentioning
confidence: 99%
“…After completion of the task, the VM is directed toward the beginning dispatcher’s I-queue for joining it. Here, the dispatcher’s I-queue length is determined to check the d-limit, the VM joins the I-queue if the length is less than the d-limit otherwise drifted toward the adjacent dispatcher I-queue and so on (Sharma et al , 2019a). The VMs are evenly distributed among I-queues based on d-limit at moderate load using dispatcher identity.…”
Section: Enhanced Quality Of Service-enabled Join Minimum Loaded Queu...mentioning
confidence: 99%
See 3 more Smart Citations