bugfix/compability issue of config files is fixed
config files of sample app1 and 2 are modified in a way to consider mobile processing unit (even their scenarios do not have task execution on the mobile devices) This issue is reported on EdgeCloudSim group: https://groups.google.com/d/msg/edgecloudsim/7dfvcUdPIak/jEQg2OK-AwAJ
This commit is contained in:
parent
e8549e0112
commit
6e37b14ba7
@ -12,6 +12,7 @@
|
|||||||
<required_core>1</required_core>
|
<required_core>1</required_core>
|
||||||
<vm_utilization_on_edge>20</vm_utilization_on_edge>
|
<vm_utilization_on_edge>20</vm_utilization_on_edge>
|
||||||
<vm_utilization_on_cloud>2</vm_utilization_on_cloud>
|
<vm_utilization_on_cloud>2</vm_utilization_on_cloud>
|
||||||
|
<vm_utilization_on_mobile>0</vm_utilization_on_mobile>
|
||||||
</application>
|
</application>
|
||||||
<application name="HEALTH_APP">
|
<application name="HEALTH_APP">
|
||||||
<usage_percentage>20</usage_percentage>
|
<usage_percentage>20</usage_percentage>
|
||||||
@ -25,6 +26,7 @@
|
|||||||
<required_core>1</required_core>
|
<required_core>1</required_core>
|
||||||
<vm_utilization_on_edge>5</vm_utilization_on_edge>
|
<vm_utilization_on_edge>5</vm_utilization_on_edge>
|
||||||
<vm_utilization_on_cloud>0.5</vm_utilization_on_cloud>
|
<vm_utilization_on_cloud>0.5</vm_utilization_on_cloud>
|
||||||
|
<vm_utilization_on_mobile>0</vm_utilization_on_mobile>
|
||||||
</application>
|
</application>
|
||||||
<application name="HEAVY_COMP_APP">
|
<application name="HEAVY_COMP_APP">
|
||||||
<usage_percentage>20</usage_percentage>
|
<usage_percentage>20</usage_percentage>
|
||||||
@ -38,6 +40,7 @@
|
|||||||
<required_core>1</required_core>
|
<required_core>1</required_core>
|
||||||
<vm_utilization_on_edge>30</vm_utilization_on_edge>
|
<vm_utilization_on_edge>30</vm_utilization_on_edge>
|
||||||
<vm_utilization_on_cloud>3</vm_utilization_on_cloud>
|
<vm_utilization_on_cloud>3</vm_utilization_on_cloud>
|
||||||
|
<vm_utilization_on_mobile>0</vm_utilization_on_mobile>
|
||||||
</application>
|
</application>
|
||||||
<application name="INFOTAINMENT_APP">
|
<application name="INFOTAINMENT_APP">
|
||||||
<usage_percentage>30</usage_percentage>
|
<usage_percentage>30</usage_percentage>
|
||||||
@ -51,5 +54,6 @@
|
|||||||
<required_core>1</required_core>
|
<required_core>1</required_core>
|
||||||
<vm_utilization_on_edge>10</vm_utilization_on_edge>
|
<vm_utilization_on_edge>10</vm_utilization_on_edge>
|
||||||
<vm_utilization_on_cloud>1</vm_utilization_on_cloud>
|
<vm_utilization_on_cloud>1</vm_utilization_on_cloud>
|
||||||
|
<vm_utilization_on_mobile>0</vm_utilization_on_mobile>
|
||||||
</application>
|
</application>
|
||||||
</applications>
|
</applications>
|
@ -24,6 +24,12 @@ mips_for_cloud_vm=10000
|
|||||||
ram_for_cloud_vm=32000
|
ram_for_cloud_vm=32000
|
||||||
storage_for_cloud_vm=1000000
|
storage_for_cloud_vm=1000000
|
||||||
|
|
||||||
|
#mobile devices has no processing unit in this scenario
|
||||||
|
core_for_mobile_vm=0
|
||||||
|
mips_for_mobile_vm=0
|
||||||
|
ram_for_mobile_vm=0
|
||||||
|
storage_for_mobile_vm=0
|
||||||
|
|
||||||
#use ',' for multiple values
|
#use ',' for multiple values
|
||||||
orchestrator_policies=NEXT_FIT
|
orchestrator_policies=NEXT_FIT
|
||||||
|
|
||||||
|
@ -24,6 +24,12 @@ mips_for_cloud_vm=100000
|
|||||||
ram_for_cloud_vm=32000
|
ram_for_cloud_vm=32000
|
||||||
storage_for_cloud_vm=1000000
|
storage_for_cloud_vm=1000000
|
||||||
|
|
||||||
|
#mobile devices has no processing unit in this scenario
|
||||||
|
core_for_mobile_vm=0
|
||||||
|
mips_for_mobile_vm=0
|
||||||
|
ram_for_mobile_vm=0
|
||||||
|
storage_for_mobile_vm=0
|
||||||
|
|
||||||
#use ',' for multiple values
|
#use ',' for multiple values
|
||||||
orchestrator_policies=NETWORK_BASED,UTILIZATION_BASED,HYBRID
|
orchestrator_policies=NETWORK_BASED,UTILIZATION_BASED,HYBRID
|
||||||
|
|
||||||
|
Loading…
Reference in New Issue
Block a user