Backfilling refers to the practice of allowing small jobs to be completed ahead of schedule as long as they do not cause the first job in the line to wait. Users are expected to offer estimates of how long jobs will take to complete in order to make these decisions possible, and these projections are often based on historical data. However, predictions are very hard and may not be accurate, particularly in cloud computing scenarios where jobs or applications run on Virtual Machines (VMs). In addition, scheduling and consolidation techniques can improve the energy efficiency and performance of applications. Consolidation involves VM migrations that can have a negative impact on workload performance and users’ costs. Backfilling can be used as an alternative technique for consolidation (short-term) and/or can be used along with consolidation (long-term). Backfilling methods are well-utilised in single computing systems, but are relatively unexplored in cloud resource allocation. A backfilling-based resource allocation and consolidation technique is proposed. Using real workloads from the Google cluster traces, we investigate the impact of backfilling on infrastructure energy efficiency and performance. For 12583 heterogeneous servers and approximately three million jobs that belong to three different applications, we observed that approximately 19% energy savings and 6% workload performance improvements are achievable using the backfilling approach. Furthermore, our evaluation suggests that using VM runtime as a criterion for the backfilling approach is approximately 3.56%–7.78% more energy and 1.91%–3.38% more performance efficient than using priority as a backfilling criterion.

Multi-access edge computing systems (MECs) bring the capabilities of cloud computing closer to the radio access network (RAN), in the context of 4G and 5G telecommunication systems, and converge with existing radio access technologies like satellite or WiFi. An MEC is a cloud server that runs at the mobile network’s edge and is installed and executed using virtual machines (VMs), containers, and/or functions. A cloudlet is similar to an MEC that consists of many servers which provide real-time, low-latency, computing services to connected users in close proximity. In connected vehicles, services may be provisioned from the cloud or edge that will be running users’ applications. As a result, when users travel across many MECs, it will be necessary to transfer their applications in a transparent manner so that performance and connectivity are not negatively affected. In this paper, we propose an effective strategy for migrating connected users’ services from one edge to another or, more likely, to a remote cloud in an MEC. A mathematical model is presented to estimate the expected times to allocate and migrate services. Our evaluations, based on real workload traces and mobility patterns, suggest that the proposed strategy “ApMove" migrates connected services while ensuring their performance ( 0.004% – 2.99% loss), reduced runtimes, therefore, users’ costs ( 4.3% – 11.63%), and minimizing the response time ( 7.45% – 9.04%). Furthermore, approximately 17.39% migrations are avoided. We also study the impacts of variations in the car’s speed and network transfer rates on service migration durations, latencies, and service execution times.

Cloud datacenters have become a backbone for today’s business and economy, which are the fastest-growing electricity consumers, globally. Numerous studies suggest that$\sim$30% of the US datacenters are comatose and the others are grossly less-utilized, which make it possible to save energy through resource consolidation techniques. However, consolidation comprises migrations that are expensive in terms of energy consumption and performance degradation, which is mostly not accounted for in many existing models, and, possibly, it could be more energy and performance efficient not to consolidate. In this paper, we investigate how migration decisions should be taken so that the migration cost is recovered, as only when migration cost has been recovered and performance is guaranteed, will energy start to be saved. We demonstrate through several experiments, using the Google workload data for 12,583 hosts and approximately one million tasks that belong to three different kinds of workload, how different allocation policies, combined with various migration approaches, will impact on datacenter’s energy and performance efficiencies. Using several plausible assumptions for containerised datacenter set-up, we suggest, that a combination of the proposed energy-performance-aware allocation (Epc-Fu) and migration (Cper) techniques, and migrating relatively long-running containers only, offers for ideal energy and performance efficiencies.