CloudSim Plus任务调度策略对比

已于 2023-04-02 20:39:36 修改
阅读量986 收藏 8
点赞数 2
分类专栏： cloudsim plus 文章标签： java
于 2021-09-12 21:46:19 首次发布
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
本文链接：https://blog.csdn.net/maohuihua123/article/details/120256618
版权
本文对比分析了两种云环境中任务调度策略：顺序调度和贪心策略。顺序策略简单地按顺序将任务分配给虚拟机，而贪心策略则根据任务执行时间和虚拟机性能进行优化分配，以降低总执行时间。实验结果显示，贪心策略平均执行时间为17.44秒，相比顺序策略的42.45秒，效率提高了59%，实现了更优的负载均衡和资源利用。
摘要由CSDN通过智能技术生成

顺序调度策略

描述： 将一组任务顺序分配给一组虚拟机

实现代码：

    private void bindCloudletToVmsRoundRobin(){
        int vmNumber = vmList.size();
        int index = 0;
        for (Cloudlet cloudlet : cloudletList) {
            cloudlet.setVm(vmList.get(index));
            index = (index + 1) % vmNumber;
        }
    }

贪心调度策略

描述： 定义一个矩阵time[i][j],表示任务i在虚拟机j所需的执行时间，显然time[i][j] = MI[i] / MIPS[j]。在初始化矩阵time前，首先将任务按MI的大小降序排序，将虚拟机按MIPS的大小升序排列。注意，重新排序后矩阵time的行号和任务ID不再一一对应，列号和虚拟机ID的对应关系也相应改变。初始化后,矩阵time的每一行、每一列的元素值都是降序排列的，然后对time做贪心。选用的贪心策略是：从矩阵中行号为0的任务开始，每次都尝试分配给最后一列对应的虚拟机，如果该选择相对于其他选择是最优的，就完成分配，否则将任务分配给运行任务最少的虚拟机，实现一种简单的负载均衡。这种方式反映了越复杂的任务需要更快的虚拟机来处理，以解决复杂任务造成的瓶颈，降低所有任务的总执行时间。

实现代码：

 private void bindCloudletToVmsTimeAwared(){
        int vmNum = vmList.size();
        int cloudletNum = cloudletList.size();
        double[][] time = new double[cloudletNum][vmNum];
        vmList.sort(Comparator.comparing(Vm::getTotalMipsCapacity));
        cloudletList.sort(Comparator.comparing(Cloudlet::getTotalLength).reversed());
        for (int i = 0; i < cloudletNum; i++) {
            for (int j = 0; j < vmNum; j++) {
                time[i][j] = cloudletList.get(i).getTotalLength() / vmList.get(j).getTotalMipsCapacity();
            }
        }
        double[] vmLoad = new double[vmNum];
        int[] vmTask = new int[vmNum];
        double minLoad = 0;
        int index = 0;

        vmLoad[vmNum-1] = time[0][vmNum-1];
        vmTask[vmNum-1] = 1;

        cloudletList.get(0).setVm(vmList.get(vmNum-1));
        for (int i = 0; i < cloudletNum; i++) {
            minLoad = vmLoad[vmNum-1] + time[i][vmNum-1];
            index = vmNum - 1;
            for (int j = vmNum -2; j >= 0; j--) {
                if (vmLoad[j] == 0) {
                    if (minLoad >= time[i][j]){
                        index = j;
                    }
                    break;
                }
                if (minLoad > vmLoad[j] + time[i][j]){
                    minLoad = vmLoad[j] + time[i][j];
                    index = j;
                } else if (minLoad == vmLoad[j] + time[i][j] && vmTask[j] < vmTask[index]){
                    index = j;
                }
            }
            vmLoad[index] += time[i][index];
            vmTask[index]++;
            cloudletList.get(i).setVm(vmList.get(index));
        }
    }

仿真实验结果

顺序策略

INFO  
================== Starting CloudSim Plus 6.3.7 ==================

INFO  0.00: DatacenterSimple1 is starting...
INFO  DatacenterBrokerSimple2 is starting...
INFO  Entities started.
INFO  0.00: DatacenterBrokerSimple2: List of 1 datacenters(s) received.
INFO  0.00: DatacenterBrokerSimple2: Trying to create Vm 0 in DatacenterSimple1
INFO  0.00: DatacenterBrokerSimple2: Trying to create Vm 1 in DatacenterSimple1
INFO  0.00: DatacenterBrokerSimple2: Trying to create Vm 2 in DatacenterSimple1
INFO  0.00: DatacenterBrokerSimple2: Trying to create Vm 3 in DatacenterSimple1
INFO  0.00: DatacenterBrokerSimple2: Trying to create Vm 4 in DatacenterSimple1
INFO  0.00: DatacenterBrokerSimple2: Trying to create Vm 5 in DatacenterSimple1
INFO  0.00: DatacenterBrokerSimple2: Trying to create Vm 6 in DatacenterSimple1
INFO  0.00: DatacenterBrokerSimple2: Trying to create Vm 7 in DatacenterSimple1
INFO  0.00: VmAllocationPolicySimple: Vm 0 has been allocated to Host 0/DC 1
INFO  0.00: VmAllocationPolicySimple: Vm 1 has been allocated to Host 0/DC 1
INFO  0.00: VmAllocationPolicySimple: Vm 2 has been allocated to Host 0/DC 1
INFO  0.00: VmAllocationPolicySimple: Vm 3 has been allocated to Host 0/DC 1
INFO  0.00: VmAllocationPolicySimple: Vm 4 has been allocated to Host 0/DC 1
INFO  0.00: VmAllocationPolicySimple: Vm 5 has been allocated to Host 0/DC 1
INFO  0.00: VmAllocationPolicySimple: Vm 6 has been allocated to Host 0/DC 1
INFO  0.00: VmAllocationPolicySimple: Vm 7 has been allocated to Host 0/DC 1
INFO  0.00: DatacenterBrokerSimple2: Sending Cloudlet 0 to Vm 0 in Host 0/DC 1.
INFO  0.00: DatacenterBrokerSimple2: Sending Cloudlet 1 to Vm 1 in Host 0/DC 1.
INFO  0.00: DatacenterBrokerSimple2: Sending Cloudlet 2 to Vm 2 in Host 0/DC 1.
INFO  0.00: DatacenterBrokerSimple2: Sending Cloudlet 3 to Vm 3 in Host 0/DC 1.
INFO  0.00: DatacenterBrokerSimple2: Sending Cloudlet 4 to Vm 4 in Host 0/DC 1.
INFO  0.00: DatacenterBrokerSimple2: Sending Cloudlet 5 to Vm 5 in Host 0/DC 1.
INFO  0.00: DatacenterBrokerSimple2: Sending Cloudlet 6 to Vm 6 in Host 0/DC 1.
INFO  0.00: DatacenterBrokerSimple2: Sending Cloudlet 7 to Vm 7 in Host 0/DC 1.
INFO  0.00: DatacenterBrokerSimple2: Sending Cloudlet 8 to Vm 0 in Host 0/DC 1.
INFO  0.00: DatacenterBrokerSimple2: Sending Cloudlet 9 to Vm 1 in Host 0/DC 1.
INFO  0.00: DatacenterBrokerSimple2: Sending Cloudlet 10 to Vm 2 in Host 0/DC 1.
INFO  0.00: DatacenterBrokerSimple2: Sending Cloudlet 11 to Vm 3 in Host 0/DC 1.
INFO  0.00: DatacenterBrokerSimple2: Sending Cloudlet 12 to Vm 4 in Host 0/DC 1.
INFO  0.00: DatacenterBrokerSimple2: Sending Cloudlet 13 to Vm 5 in Host 0/DC 1.
INFO  0.00: DatacenterBrokerSimple2: Sending Cloudlet 14 to Vm 6 in Host 0/DC 1.
INFO  0.00: DatacenterBrokerSimple2: Sending Cloudlet 15 to Vm 7 in Host 0/DC 1.
INFO  0.00: DatacenterBrokerSimple2: Sending Cloudlet 16 to Vm 0 in Host 0/DC 1.
INFO  0.00: DatacenterBrokerSimple2: Sending Cloudlet 17 to Vm 1 in Host 0/DC 1.
INFO  0.00: DatacenterBrokerSimple2: Sending Cloudlet 18 to Vm 2 in Host 0/DC 1.
INFO  0.00: DatacenterBrokerSimple2: Sending Cloudlet 19 to Vm 3 in Host 0/DC 1.
INFO  0.00: DatacenterBrokerSimple2: All waiting Cloudlets submitted to some VM.
INFO  0.61: DatacenterBrokerSimple2: Cloudlet 6 finished in Vm 6 and returned to broker.
INFO  0.96: DatacenterBrokerSimple2: Cloudlet 7 finished in Vm 7 and returned to broker.
INFO  1.75: DatacenterBrokerSimple2: Cloudlet 1 finished in Vm 1 and returned to broker.
INFO  2.89: DatacenterBrokerSimple2: Cloudlet 14 finished in Vm 6 and returned to broker.
INFO  3.18: DatacenterBrokerSimple2: Cloudlet 0 finished in Vm 0 and returned to broker.
INFO  3.60: DatacenterBrokerSimple2: Cloudlet 15 finished in Vm 7 and returned to broker.
INFO  4.37: DatacenterBrokerSimple2: Cloudlet 5 finished in Vm 5 and returned to broker.
INFO  4.92: DatacenterBrokerSimple2: Cloudlet 2 finished in Vm 2 and returned to broker.
INFO  6.12: DatacenterBrokerSimple2: Cloudlet 9 finished in Vm 1 and returned to broker.
INFO  6.34: DatacenterBrokerSimple2: Cloudlet 8 finished in Vm 0 and returned to broker.
INFO  6.78: DatacenterBrokerSimple2: Cloudlet 3 finished in Vm 3 and returned to broker.
INFO  7.33: DatacenterBrokerSimple2: Cloudlet 13 finished in Vm 5 and returned to broker.
INFO  9.44: DatacenterBrokerSimple2: Cloudlet 16 finished in Vm 0 and returned to broker.
INFO  10.78: DatacenterBrokerSimple2: Cloudlet 11 finished in Vm 3 and returned to broker.
INFO  12.78: DatacenterBrokerSimple2: Cloudlet 4 finished in Vm 4 and returned to broker.
INFO  13.31: DatacenterBrokerSimple2: Cloudlet 17 finished in Vm 1 and returned to broker.
INFO  14.98: DatacenterBrokerSimple2: Cloudlet 10 finished in Vm 2 and returned to broker.
INFO  19.20: DatacenterBrokerSimple2: Cloudlet 19 finished in Vm 3 and returned to broker.
INFO  19.95: DatacenterBrokerSimple2: Cloudlet 18 finished in Vm 2 and returned to broker.
INFO  30.11: DatacenterBrokerSimple2: Cloudlet 12 finished in Vm 4 and returned to broker.
INFO  30.12: Processing last events before simulation shutdown.
INFO  30.12: DatacenterBrokerSimple2 is shutting down...
INFO  30.12: DatacenterBrokerSimple2: Requesting Vm 7 destruction.
INFO  30.12: DatacenterBrokerSimple2: Requesting Vm 6 destruction.
INFO  30.12: DatacenterBrokerSimple2: Requesting Vm 5 destruction.
INFO  30.12: DatacenterBrokerSimple2: Requesting Vm 4 destruction.
INFO  30.12: DatacenterBrokerSimple2: Requesting Vm 3 destruction.
INFO  30.12: DatacenterBrokerSimple2: Requesting Vm 2 destruction.
INFO  30.12: DatacenterBrokerSimple2: Requesting Vm 1 destruction.
INFO  30.12: DatacenterBrokerSimple2: Requesting Vm 0 destruction.
INFO  30.12: DatacenterSimple: Vm 7 destroyed on Host 0/DC 1. 
INFO  30.12: DatacenterSimple: Vm 6 destroyed on Host 0/DC 1. 
INFO  30.12: DatacenterSimple: Vm 5 destroyed on Host 0/DC 1. 
INFO  30.12: DatacenterSimple: Vm 4 destroyed on Host 0/DC 1. 
INFO  30.12: DatacenterSimple: Vm 3 destroyed on Host 0/DC 1. 
INFO  30.12: DatacenterSimple: Vm 2 destroyed on Host 0/DC 1. 
INFO  30.12: DatacenterSimple: Vm 1 destroyed on Host 0/DC 1. 
INFO  30.12: DatacenterSimple: Vm 0 destroyed on Host 0/DC 1. 
INFO  Simulation: No more future events

INFO  CloudInformationService0: Notify all CloudSim Plus entities to shutdown.

INFO  
================== Simulation finished at time 30.12 ==================

DEBUG DeferredQueue >> max size: 19 added to middle: 0 added to tail: 200


                                              SIMULATION RESULTS

Cloudlet|Status |DC|Host|Host PEs |VM|VM PEs   |VM PEs   |CloudletLen|CloudletPEs|StartTime|FinishTime|ExecTime
      ID|       |ID|  ID|CPU cores|ID|CPU cores|     MIPS|         MI|  CPU cores|  Seconds|   Seconds| Seconds
---------------------------------------------------------------------------------------------------------------
       6|SUCCESS| 1|   0|        8| 6|        1|   8238.0|       5007|          1|     0.00|      0.61|    0.61
       7|SUCCESS| 1|   0|        8| 7|        1|   8942.0|       8531|          1|     0.00|      0.96|    0.96
       1|SUCCESS| 1|   0|        8| 1|        1|   2985.0|       5187|          1|     0.00|      1.75|    1.75
      14|SUCCESS| 1|   0|        8| 6|        1|   8238.0|      18623|          1|     0.62|      2.89|    2.27
       0|SUCCESS| 1|   0|        8| 0|        1|   6739.0|      21330|          1|     0.00|      3.18|    3.18
      15|SUCCESS| 1|   0|        8| 7|        1|   8942.0|      23437|          1|     0.96|      3.60|    2.63
       5|SUCCESS| 1|   0|        8| 5|        1|   8236.0|      35912|          1|     0.00|      4.37|    4.37
       2|SUCCESS| 1|   0|        8| 2|        1|   3513.0|      17247|          1|     0.00|      4.92|    4.92
       9|SUCCESS| 1|   0|        8| 1|        1|   2985.0|      13010|          1|     1.75|      6.12|    4.37
       8|SUCCESS| 1|   0|        8| 0|        1|   6739.0|      21281|          1|     3.18|      6.34|    3.17
       3|SUCCESS| 1|   0|        8| 3|        1|   4704.0|      31823|          1|     0.00|      6.78|    6.78
      13|SUCCESS| 1|   0|        8| 5|        1|   8236.0|      24262|          1|     4.37|      7.33|    2.96
      16|SUCCESS| 1|   0|        8| 0|        1|   6739.0|      20712|          1|     6.35|      9.44|    3.08
      11|SUCCESS| 1|   0|        8| 3|        1|   4704.0|      18801|          1|     6.78|     10.78|    4.01
       4|SUCCESS| 1|   0|        8| 4|        1|   1638.0|      20894|          1|     0.00|     12.78|   12.78
      17|SUCCESS| 1|   0|        8| 1|        1|   2985.0|      21426|          1|     6.13|     13.31|    7.19
      10|SUCCESS| 1|   0|        8| 2|        1|   3513.0|      35315|          1|     4.92|     14.98|   10.06
      19|SUCCESS| 1|   0|        8| 3|        1|   4704.0|      39488|          1|    10.79|     19.20|    8.40
      18|SUCCESS| 1|   0|        8| 2|        1|   3513.0|      17378|          1|    14.99|     19.95|    4.96
      12|SUCCESS| 1|   0|        8| 4|        1|   1638.0|      28379|          1|    12.78|     30.11|   17.33
---------------------------------------------------------------------------------------------------------------

贪心策略

INFO  
================== Starting CloudSim Plus 6.3.7 ==================

INFO  0.00: DatacenterSimple1 is starting...
INFO  DatacenterBrokerSimple2 is starting...
INFO  Entities started.
INFO  0.00: DatacenterBrokerSimple2: List of 1 datacenters(s) received.
INFO  0.00: DatacenterBrokerSimple2: Trying to create Vm 0 in DatacenterSimple1
INFO  0.00: DatacenterBrokerSimple2: Trying to create Vm 1 in DatacenterSimple1
INFO  0.00: DatacenterBrokerSimple2: Trying to create Vm 2 in DatacenterSimple1
INFO  0.00: DatacenterBrokerSimple2: Trying to create Vm 3 in DatacenterSimple1
INFO  0.00: DatacenterBrokerSimple2: Trying to create Vm 4 in DatacenterSimple1
INFO  0.00: DatacenterBrokerSimple2: Trying to create Vm 5 in DatacenterSimple1
INFO  0.00: DatacenterBrokerSimple2: Trying to create Vm 6 in DatacenterSimple1
INFO  0.00: DatacenterBrokerSimple2: Trying to create Vm 7 in DatacenterSimple1
INFO  0.00: VmAllocationPolicySimple: Vm 0 has been allocated to Host 0/DC 1
INFO  0.00: VmAllocationPolicySimple: Vm 1 has been allocated to Host 0/DC 1
INFO  0.00: VmAllocationPolicySimple: Vm 2 has been allocated to Host 0/DC 1
INFO  0.00: VmAllocationPolicySimple: Vm 3 has been allocated to Host 0/DC 1
INFO  0.00: VmAllocationPolicySimple: Vm 4 has been allocated to Host 0/DC 1
INFO  0.00: VmAllocationPolicySimple: Vm 5 has been allocated to Host 0/DC 1
INFO  0.00: VmAllocationPolicySimple: Vm 6 has been allocated to Host 0/DC 1
INFO  0.00: VmAllocationPolicySimple: Vm 7 has been allocated to Host 0/DC 1
INFO  0.00: DatacenterBrokerSimple2: Sending Cloudlet 0 to Vm 6 in Host 0/DC 1.
INFO  0.00: DatacenterBrokerSimple2: Sending Cloudlet 1 to Vm 5 in Host 0/DC 1.
INFO  0.00: DatacenterBrokerSimple2: Sending Cloudlet 2 to Vm 4 in Host 0/DC 1.
INFO  0.00: DatacenterBrokerSimple2: Sending Cloudlet 3 to Vm 7 in Host 0/DC 1.
INFO  0.00: DatacenterBrokerSimple2: Sending Cloudlet 4 to Vm 6 in Host 0/DC 1.
INFO  0.00: DatacenterBrokerSimple2: Sending Cloudlet 5 to Vm 3 in Host 0/DC 1.
INFO  0.00: DatacenterBrokerSimple2: Sending Cloudlet 6 to Vm 2 in Host 0/DC 1.
INFO  0.00: DatacenterBrokerSimple2: Sending Cloudlet 7 to Vm 1 in Host 0/DC 1.
INFO  0.00: DatacenterBrokerSimple2: Sending Cloudlet 8 to Vm 0 in Host 0/DC 1.
INFO  0.00: DatacenterBrokerSimple2: Sending Cloudlet 9 to Vm 4 in Host 0/DC 1.
INFO  0.00: DatacenterBrokerSimple2: Sending Cloudlet 10 to Vm 5 in Host 0/DC 1.
INFO  0.00: DatacenterBrokerSimple2: Sending Cloudlet 11 to Vm 7 in Host 0/DC 1.
INFO  0.00: DatacenterBrokerSimple2: Sending Cloudlet 12 to Vm 6 in Host 0/DC 1.
INFO  0.00: DatacenterBrokerSimple2: Sending Cloudlet 13 to Vm 2 in Host 0/DC 1.
INFO  0.00: DatacenterBrokerSimple2: Sending Cloudlet 14 to Vm 3 in Host 0/DC 1.
INFO  0.00: DatacenterBrokerSimple2: Sending Cloudlet 15 to Vm 5 in Host 0/DC 1.
INFO  0.00: DatacenterBrokerSimple2: Sending Cloudlet 16 to Vm 4 in Host 0/DC 1.
INFO  0.00: DatacenterBrokerSimple2: Sending Cloudlet 17 to Vm 1 in Host 0/DC 1.
INFO  0.00: DatacenterBrokerSimple2: Sending Cloudlet 18 to Vm 5 in Host 0/DC 1.
INFO  0.00: DatacenterBrokerSimple2: Sending Cloudlet 19 to Vm 0 in Host 0/DC 1.
INFO  0.00: DatacenterBrokerSimple2: All waiting Cloudlets submitted to some VM.
INFO  5.65: DatacenterBrokerSimple2: Cloudlet 3 finished in Vm 7 and returned to broker.
INFO  6.19: DatacenterBrokerSimple2: Cloudlet 0 finished in Vm 6 and returned to broker.
INFO  7.83: DatacenterBrokerSimple2: Cloudlet 2 finished in Vm 4 and returned to broker.
INFO  7.95: DatacenterBrokerSimple2: Cloudlet 1 finished in Vm 5 and returned to broker.
INFO  8.45: DatacenterBrokerSimple2: Cloudlet 11 finished in Vm 7 and returned to broker.
INFO  10.21: DatacenterBrokerSimple2: Cloudlet 6 finished in Vm 2 and returned to broker.
INFO  10.40: DatacenterBrokerSimple2: Cloudlet 5 finished in Vm 3 and returned to broker.
INFO  11.77: DatacenterBrokerSimple2: Cloudlet 7 finished in Vm 1 and returned to broker.
INFO  11.86: DatacenterBrokerSimple2: Cloudlet 10 finished in Vm 5 and returned to broker.
INFO  11.86: DatacenterBrokerSimple2: Cloudlet 4 finished in Vm 6 and returned to broker.
INFO  11.90: DatacenterBrokerSimple2: Cloudlet 9 finished in Vm 4 and returned to broker.
INFO  12.40: DatacenterBrokerSimple2: Cloudlet 8 finished in Vm 0 and returned to broker.
INFO  13.34: DatacenterBrokerSimple2: Cloudlet 14 finished in Vm 3 and returned to broker.
INFO  13.51: DatacenterBrokerSimple2: Cloudlet 15 finished in Vm 5 and returned to broker.
INFO  13.57: DatacenterBrokerSimple2: Cloudlet 16 finished in Vm 4 and returned to broker.
INFO  13.90: DatacenterBrokerSimple2: Cloudlet 12 finished in Vm 6 and returned to broker.
INFO  14.20: DatacenterBrokerSimple2: Cloudlet 13 finished in Vm 2 and returned to broker.
INFO  14.48: DatacenterBrokerSimple2: Cloudlet 17 finished in Vm 1 and returned to broker.
INFO  14.56: DatacenterBrokerSimple2: Cloudlet 19 finished in Vm 0 and returned to broker.
INFO  14.79: DatacenterBrokerSimple2: Cloudlet 18 finished in Vm 5 and returned to broker.
INFO  14.80: Processing last events before simulation shutdown.
INFO  14.80: DatacenterBrokerSimple2 is shutting down...
INFO  14.80: DatacenterBrokerSimple2: Requesting Vm 7 destruction.
INFO  14.80: DatacenterBrokerSimple2: Requesting Vm 6 destruction.
INFO  14.80: DatacenterBrokerSimple2: Requesting Vm 5 destruction.
INFO  14.80: DatacenterBrokerSimple2: Requesting Vm 4 destruction.
INFO  14.80: DatacenterBrokerSimple2: Requesting Vm 3 destruction.
INFO  14.80: DatacenterBrokerSimple2: Requesting Vm 2 destruction.
INFO  14.80: DatacenterBrokerSimple2: Requesting Vm 1 destruction.
INFO  14.80: DatacenterBrokerSimple2: Requesting Vm 0 destruction.
INFO  14.80: DatacenterSimple: Vm 7 destroyed on Host 0/DC 1. 
INFO  14.80: DatacenterSimple: Vm 6 destroyed on Host 0/DC 1. 
INFO  14.80: DatacenterSimple: Vm 5 destroyed on Host 0/DC 1. 
INFO  14.80: DatacenterSimple: Vm 4 destroyed on Host 0/DC 1. 
INFO  14.80: DatacenterSimple: Vm 3 destroyed on Host 0/DC 1. 
INFO  14.80: DatacenterSimple: Vm 2 destroyed on Host 0/DC 1. 
INFO  14.80: DatacenterSimple: Vm 1 destroyed on Host 0/DC 1. 
INFO  14.80: DatacenterSimple: Vm 0 destroyed on Host 0/DC 1. 
INFO  Simulation: No more future events

INFO  CloudInformationService0: Notify all CloudSim Plus entities to shutdown.

INFO  
================== Simulation finished at time 14.80 ==================

DEBUG DeferredQueue >> max size: 19 added to middle: 0 added to tail: 222


                                              SIMULATION RESULTS

Cloudlet|Status |DC|Host|Host PEs |VM|VM PEs   |VM PEs   |CloudletLen|CloudletPEs|StartTime|FinishTime|ExecTime
      ID|       |ID|  ID|CPU cores|ID|CPU cores|     MIPS|         MI|  CPU cores|  Seconds|   Seconds| Seconds
---------------------------------------------------------------------------------------------------------------
       3|SUCCESS| 1|   0|        8| 7|        1|   8129.0|      45902|          1|     0.00|      5.65|    5.65
       0|SUCCESS| 1|   0|        8| 6|        1|   8051.0|      49760|          1|     0.00|      6.19|    6.19
       2|SUCCESS| 1|   0|        8| 4|        1|   5899.0|      46114|          1|     0.00|      7.83|    7.83
       1|SUCCESS| 1|   0|        8| 5|        1|   6029.0|      47863|          1|     0.00|      7.95|    7.95
      11|SUCCESS| 1|   0|        8| 7|        1|   8129.0|      22652|          1|     5.66|      8.45|    2.80
       6|SUCCESS| 1|   0|        8| 2|        1|   3770.0|      38452|          1|     0.00|     10.21|   10.21
       5|SUCCESS| 1|   0|        8| 3|        1|   3794.0|      39416|          1|     0.00|     10.40|   10.40
       7|SUCCESS| 1|   0|        8| 1|        1|   3244.0|      38160|          1|     0.00|     11.77|   11.77
      10|SUCCESS| 1|   0|        8| 5|        1|   6029.0|      23515|          1|     7.95|     11.86|    3.91
       4|SUCCESS| 1|   0|        8| 6|        1|   8051.0|      45564|          1|     6.19|     11.86|    5.67
       9|SUCCESS| 1|   0|        8| 4|        1|   5899.0|      23958|          1|     7.83|     11.90|    4.07
       8|SUCCESS| 1|   0|        8| 0|        1|   2873.0|      35583|          1|     0.00|     12.40|   12.40
      14|SUCCESS| 1|   0|        8| 3|        1|   3794.0|      11134|          1|    10.40|     13.34|    2.94
      15|SUCCESS| 1|   0|        8| 5|        1|   6029.0|       9909|          1|    11.86|     13.51|    1.65
      16|SUCCESS| 1|   0|        8| 4|        1|   5899.0|       9796|          1|    11.90|     13.57|    1.67
      12|SUCCESS| 1|   0|        8| 6|        1|   8051.0|      16374|          1|    11.86|     13.90|    2.04
      13|SUCCESS| 1|   0|        8| 2|        1|   3770.0|      14989|          1|    10.21|     14.20|    3.99
      17|SUCCESS| 1|   0|        8| 1|        1|   3244.0|       8727|          1|    11.77|     14.48|    2.71
      19|SUCCESS| 1|   0|        8| 0|        1|   2873.0|       6194|          1|    12.40|     14.56|    2.17
      18|SUCCESS| 1|   0|        8| 5|        1|   6029.0|       7622|          1|    13.51|     14.79|    1.27
---------------------------------------------------------------------------------------------------------------

任务的总执行时间

描述： 两种调度方式均重复执行十次实验，取平均值。

结果：

算法\实验ID12345678910
Round Robin23.5133.8167.2948.8555.3338.1229.2921.4151.7459.13
Greedy15.7319.3920.2211.7221.6523.3417.1516.6014.4214.15

分析：

顺序调度策略的平均执行时间：
A v e r a g e R R = 42.45 \text Average_{RR}=\text {42.45} AverageRR​=42.45
贪心调度策略的平均执行时间：
A v e r a g e G r e e d y = 17.44 \text Average_{Greedy}=\text {17.44} AverageGreedy​=17.44
总结： 贪心策略比顺序策略节省了59%的总执行时间。

参考

《分布式计算、云计算与大数据》林伟伟

沧浪之水NaN
关注
  • 2
    点赞
  • 踩
  • 8
    收藏
    觉得还不错? 一键收藏
  • 0
    评论
专栏目录
Spark 中任务调度机制
a1786742005的博客
09-04 1638
一、Spark 任务调度机制概述 在生产环境下，Spark 集群的部署方式一般为 YARN-Cluster 模式，下面内核分析中默认集群的部署方式为 YARN-Cluster 模式。 Driver 线程主要是初始化 SparkContext 对象，准备运行所需的上下文，然后一方面保持与 ApplicationMaster 的 RPC 连接，通过 ApplicationMaster 申请资源，另一方面根据用户业务逻辑开始调度任务，将任务下发到已有的空闲 Executor 上。 当 ResourceManage
Linux 任务调度策略
mtofum的专栏
03-06 3326
Linux任务调度策略linux内核的三种调度方法 SCHED_OTHER 分时调度策略 SCHED_FIFO实时调度策略，先到先服务 SCHED_RR实时调度策略，时间片轮转
cloudsim中时间共享调度策略和空间共享调度策略
m0_37671741的博客
11-08 1341
Cloudsim支持两个层次的vm分配:第一个层次是主机级别，即指定将为每个vm分配每个核的总处理能力；第二个层次是虚拟机级别，即虚拟机将固定数量的可用处理能力分配给在其执行引擎内托管的每个任务单元。 为此，cloudsim实现了基于时间共享和空间共享的调度策略。 时间共享：通过分配时间片进行共享，可以同时进行，不存在排队。 空间共享：同时占用空间，但是完成一个以后才能开始另一个，存在排队。...
任务调度策略
　　　　　KISSMonX
08-28 739
用遗传算法GA改进CloudSim自带的资源调度策略
morein2008的专栏
12-24 1001
首先理解云计算里，资源调度的含义： 看了很多云计算资源调度和任务调度方面的论文，发现很多情况下这两者的意义是相同的，不知道这两者是同一件事的不同表述还是我没分清吧，任务调度或者资源调度大概就是讲这样一件事情： 用户有n个计算任务(Task)，{t1,t2,t3,...tm}，将这n个任务分配到m个资源(其实就是指虚拟机，Virtual Machine)上，用这m个资源来计算这n个任务(注意，一般...
数据平台任务调度-策略设计
半僧的大数据杂谈
07-13 492
大数据平台任务调度策略设计时需要考虑的因素以及调度平台的核心工作原理介绍。
第6讲 任务调度算法_task_任务调度算法_cloudsim_
10-01
本讲的主题"第6讲 任务调度算法_task_任务调度算法_cloudsim_"聚焦于如何有效地管理计算资源，特别是通过CloudSim工具来模拟和研究任务调度策略。CloudSim是一个广泛使用的开源仿真框架，专门用于云计算环境的研究。...
基于稳定婚姻算法和cloudsim框架的云计算任务调度模拟Java源码(本科毕设).zip
08-18
【资源说明】 1、该资源内项目代码都是经过测试运行成功，功能ok的情况下才上传的，请放心下载使用！ 2、本项目适合计算机相关专业(如计...基于稳定婚姻算法和cloudsim框架的云计算任务调度模拟Java源码(本科毕设).zip
VMScheduling:模拟环境应用不同的 VM 调度策略（使用 CloudSim）
06-20
Vicc 项目：自制 VM 调度程序 该项目旨在为给定的 IaaS 云开发不同的 Vm 调度程序。 这是在作为研究生级别的项目完成。 每个调度程序对于云客户或云提供商都具有有意义的属性。 该实现是通过 IaaS 云模拟器。 ...
cloudsimplus-gateway:用于Cloud Sim Plus框架的py4j网关
05-24
CloudSim +-Py4j网关 魔法： ./gradlew build -构建和运行测试 ./gradlew dockerBuildImage构建图像 致谢 Project使用CloudSim Plus框架：功能齐全，高度可扩展且易于使用的Java 8+框架，用于对云计算基础架构和服务进行建模和仿真。 你可以在找到它。 源代码
CloudSim云仿真框架介绍
01-15
CloudSim云仿真框架介绍，是本人翻译的一篇关于CloudSim非常棒的一篇英文论文
CloudSim_GA_cloudsim_
10-01
在CloudSim_GA中，每个个体代表一种任务调度策略，由一组参数（基因）组成，这些参数可能包括任务的优先级、执行时间预测、资源分配策略等。通过模拟种群的进化过程，GA能够逐步搜索出接近最优解的调度策略。 ...
ThreadPoolExecutor任务调度策略
阿振的博客
02-01 562
execute：  execute方法时暴露给开发者提交任务的方法，这个方法就是整个线程池的入口。当然还有submit类方法，实际上也是调用了execute方法。 public void execute(Runnable command) { if (command == null) throw new NullPointerException(); i
201403-5 任务调度 解题策略探讨
宋旭升的博客
09-06 833
#include<iostream> #include<fstream> #include<stdlib.h> #include<map> #include<time.h> #include<set> #include<iomanip> #include<algorithm> #include<...
spark有什么任务调度策略配置
weixin_35754962的博客
02-12 242
Spark 有以下几种任务调度策略配置: 公平调度 (Fair Scheduling): 根据每个应用程序的任务数量来均衡分配资源，保证所有应用程序都有相同的 CPU 时间片。 轮询调度 (Round Robin Scheduling): 在每个应用程序之间循环分配任务，保证每个应用程序都有相等的机会获得资源。 随机调度 (Random Scheduling): 随机分配任务给每个应用程序...
任务调度框架对比
It_sharp的博客
06-26 652
前言 任务调度框架的演变：从单机到分布式
探索CloudSimplus：一个高效云管理平台的深度剖析
最新发布
gitblog_00094的博客
04-27 366
探索CloudSimplus：一个高效云管理平台的深度剖析 cloudsimplusState-of-the-art Framework ???? for Cloud Computing ⛅️ Simulation: a modern, full-featured, easier-to-use, highly extensible ????, faster ???? and more accurate ☕️ Ja...
cloudsim资源调度侧策略的研究目的
07-16
研究CloudSim资源调度策略的目的是为了优云计算环境下的资源分配和任务调度，以提高系统的性能和效率。具体而言，资源调度策略的研究目的包括以下几个方面： 1. 提高任务完成时间：资源调度策略的一个主要目标是...
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值