|
65 | 65 | * 3 VMs with 2 PEs each one; |
66 | 66 | * and 1 cloudlet by VM, each one having the same number of PEs from its VM. |
67 | 67 | * |
68 | | - * |
69 | 68 | * <p>The example then performs VM migration using |
70 | 69 | * a {@link VmAllocationPolicyMigrationBestFitStaticThreshold}. |
71 | 70 | * Such a policy migrates VMs based on |
|
79 | 78 | * Each cloudlet will start using 80% of its VM CPU. |
80 | 79 | * As the VM 0 will run one Cloudlet and requires just 2 PEs from Host 0 (which has 4 PEs), |
81 | 80 | * the initial Host CPU usage will be just 40% (1 VM using 80% of 2 PEs from a total of 4 Host PEs = 0.8*2 / 4). |
| 81 | + * </p> |
82 | 82 | * |
| 83 | + * <p> |
83 | 84 | * Allocating a second VM into Host 0 would double the Host CPU utilization, |
84 | 85 | * overreaching its upper utilization threshold (defined as 70%). |
85 | 86 | * This way, VMs 1 and 2 are allocated to Host 1 which has 5 PEs. |
|
90 | 91 | * enable VM migration. |
91 | 92 | * The example uses a {@link UtilizationModelDynamic} to define that CPU usage of cloudlets |
92 | 93 | * increases along simulation time. |
93 | | - * The first 2 Cloudlets all start with a usage of 80% of CPU, |
| 94 | + * The first 2 Cloudlets start with a usage of 80% of CPU, |
94 | 95 | * which increases along the time (see {@link #CLOUDLET_CPU_INCREMENT_PER_SECOND}). |
95 | 96 | * The third Cloudlet starts at a lower CPU usage and increases in the same way. |
96 | 97 | * </p> |
97 | 98 | * |
98 | 99 | * <p>Some constants are used to create simulation objects such as |
99 | 100 | * {@link DatacenterSimple}, {@link Host} and {@link Vm}. |
100 | 101 | * The values of these constants were careful and accordingly chosen to allow: |
101 | | - * (i) migration of VMs due to either under and overloaded hosts; and (ii) |
102 | | - * the researcher to know exactly how the simulation will run |
| 102 | + * (i) migration of VMs due to either under and overloaded hosts; |
| 103 | + * and (ii) the researcher to know exactly how the simulation will run |
103 | 104 | * and what will be the final results. |
104 | 105 | * </p> |
105 | 106 | * |
|
108 | 109 | * (i) hosts CPU capacity and number of PEs, |
109 | 110 | * (ii) VMs and cloudlets requirements and |
110 | 111 | * (iii) even VM bandwidth (which defines the VM migration time). |
| 112 | + * </p> |
111 | 113 | * |
| 114 | + * <p> |
112 | 115 | * This way, if you want to change these values, you must |
113 | 116 | * define new appropriated ones to allow the simulation |
114 | 117 | * to run correctly.</p> |
|
0 commit comments