<?xml version="1.0" encoding="UTF-8"?>
<item xmlns="http://omeka.org/schemas/omeka-xml/v5" itemId="14098" public="1" featured="0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://omeka.org/schemas/omeka-xml/v5 http://omeka.org/schemas/omeka-xml/v5/omeka-xml-5-0.xsd" uri="https://archives.christuniversity.in/items/show/14098?output=omeka-xml" accessDate="2026-05-03T07:45:59+00:00">
  <collection collectionId="5">
    <elementSetContainer>
      <elementSet elementSetId="1">
        <name>Dublin Core</name>
        <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
        <elementContainer>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="64">
                <text>Articles</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </collection>
  <itemType itemTypeId="19">
    <name>Article</name>
    <description>Faculty Publications -Articles</description>
  </itemType>
  <elementSetContainer>
    <elementSet elementSetId="1">
      <name>Dublin Core</name>
      <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
      <elementContainer>
        <element elementId="50">
          <name>Title</name>
          <description>A name given to the resource</description>
          <elementTextContainer>
            <elementText elementTextId="94241">
              <text>An efficient load balancing in cloud computing using hybrid Harris hawks optimization and cuckoo search algorithm</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="49">
          <name>Subject</name>
          <description>The topic of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="94242">
              <text>Cloud computing; Hybrid Harris hawks optimization-cuckoo search algorithm; Load balancing; Quality of service; Service level agreement; Task scheduling</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="41">
          <name>Description</name>
          <description>An account of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="94243">
              <text>Cloud computing has rapidly emerged as a burgeoning research field in recent times. However, despite this growth, a comprehensive examination of this domain reveals persistent issues in the application of cloud-based systems concerning workload distribution. The abundance of resources and virtual machines (VMs) within cloud computing underscores the importance of efficient task allocation as a critical process. Within the infrastructure as a service (IaaS) architecture, load balancing (LB) remains a pivotal but challenging task. The occurrence of overloaded or underloaded hosts/servers during cloud access is undesirable, as it leads to operational delays and system performance degradation. To address LB issues effectively, it is imperative to deploy a proficient access scheduling algorithm capable of distributing tasks across the available resources. A novel approach was introduced by combining the Harris hawks optimization and cuckoo search algorithm (HHO-CSA), with a specific focus on critical service level agreement (SLA) parameters, particularly deadlines, to uphold LB in a cloud environment. The primary objective of the hybrid HHO-CSA methodology is to provide task attributes, resource allocation, VMs prioritization, and quality of service (QoS) to clients within cloud computing applications. The outcome analysis reveals that the proposed hybrid HHO-CSA algorithm results in a resource utilization reduction of 52%, with an execution time of 529.84 ms and a makespan of 638.88 ms. These values outperform those of existing SLA-based LB algorithms. Effective task scheduling plays a pivotal role in ensuring the seamless execution of tasks within a cloud system, while LB significantly aligns with the SLAs available to users. Drawing insights from the existing literature, the suggested hybrid HHO-CSA method addresses the research gap by effectively mitigating the challenges.  2023, Accent Social and Welfare Society. All rights reserved.</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="39">
          <name>Creator</name>
          <description>An entity primarily responsible for making the resource</description>
          <elementTextContainer>
            <elementText elementTextId="94244">
              <text>Pani A.K.; Manohar M.; Thomas M.; Kumar P.</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="48">
          <name>Source</name>
          <description>A related resource from which the described resource is derived</description>
          <elementTextContainer>
            <elementText elementTextId="94245">
              <text>International Journal of Advanced Technology and Engineering Exploration, Vol-10, No. 105, pp. 1050-1062.</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="45">
          <name>Publisher</name>
          <description>An entity responsible for making the resource available</description>
          <elementTextContainer>
            <elementText elementTextId="94246">
              <text>Accent Social and Welfare Society</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="40">
          <name>Date</name>
          <description>A point or period of time associated with an event in the lifecycle of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="94247">
              <text>2023-01-01</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="43">
          <name>Identifier</name>
          <description>An unambiguous reference to the resource within a given context</description>
          <elementTextContainer>
            <elementText elementTextId="94248">
              <text>&lt;a href="https://doi.org/10.19101/IJATEE.2022.10100466" target="_blank" rel="noreferrer noopener"&gt;https://doi.org/10.19101/IJATEE.2022.10100466&lt;/a&gt;
&lt;br /&gt;&lt;br /&gt;&lt;a href="https://www.scopus.com/inward/record.uri?eid=2-s2.0-85170093103&amp;amp;doi=10.19101%2FIJATEE.2022.10100466&amp;amp;partnerID=40&amp;amp;md5=2d5945e0d43fea281fa5081d2e64e705" target="_blank" rel="noreferrer noopener"&gt;https://www.scopus.com/inward/record.uri?eid=2-s2.0-85170093103&amp;amp;doi=10.19101%2fIJATEE.2022.10100466&amp;amp;partnerID=40&amp;amp;md5=2d5945e0d43fea281fa5081d2e64e705&lt;/a&gt;</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="47">
          <name>Rights</name>
          <description>Information about rights held in and over the resource</description>
          <elementTextContainer>
            <elementText elementTextId="94249">
              <text>All Open Access; Gold Open Access</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="46">
          <name>Relation</name>
          <description>A related resource</description>
          <elementTextContainer>
            <elementText elementTextId="94250">
              <text>ISSN: 23945443</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="42">
          <name>Format</name>
          <description>The file format, physical medium, or dimensions of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="94251">
              <text>Online</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="44">
          <name>Language</name>
          <description>A language of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="94252">
              <text>English</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="51">
          <name>Type</name>
          <description>The nature or genre of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="94253">
              <text>Article</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="38">
          <name>Coverage</name>
          <description>The spatial or temporal topic of the resource, the spatial applicability of the resource, or the jurisdiction under which the resource is relevant</description>
          <elementTextContainer>
            <elementText elementTextId="94254">
              <text>Pani A.K., Department of Computer Science and Engineering, CHRIST (Deemed to be University), Bengaluru, India; Manohar M., Department of Computer Science and Engineering, CHRIST (Deemed to be University), Bengaluru, India; Thomas M., School of Computer Science, RV University, Bengaluru, India; Kumar P., Department of Computer Science and Engineering, Motihari College of Engineering, Bihar, India</text>
            </elementText>
          </elementTextContainer>
        </element>
      </elementContainer>
    </elementSet>
  </elementSetContainer>
</item>
