Simulation is not complete all cloudlets execution

[duaa h]

I run some cloudlets in Cloudsim plus but most of them are not finished at the end of simulation. This massage is shows:

It had a total of 67 cloudlets (running + waiting). Some events may have been missed. You can try: 

(a) decreasing CloudSim's minTimeBetweenEvents and/or Datacenter's schedulingInterval attribute; 

(b) increasing broker's Vm destruction delay for idle VMs if you set it to zero;

 (c) defining Cloudlets with smaller length (your Datacenter's scheduling interval may be smaller than the time to finish some Cloudlets).

 

I tried all suggested solutions but the problem is still.

When I decrease number of hosts, number of finished cloudlets are increased but still few. 

what another configuration or variables affect on completing cloudlets execution?

my configuration:

number of cloudlets=71

 CLOUDLET_LENGTH = 1000

 number of HOSTS = 2
 HOST_PES = 224
 HOST_RAM = 917504  (in Megabytes )

 HOST_BW = 10000 (in Megabits/s)
 HOST_STORAGE = 1000000  (in Megabytes)
 HOST_MIPS = 1000;

the cloudlets are read from google trace file

[Manoel Campos]

I think your cloudlet length is too short for the Host MIPS capacity.

A cloudlet with 1000 MI running inside a VM/Host with 1000 MIPS CPU may finish in just one second.

I've found some issues when cloudlets are too short.

Maybe message (c) is misleading. You should try to opposite: increase cloudlet len.

Let me know if that worked.

Manoel Campos da Silva Filho Software Engineer

Computer Science and Engineering Ph.D. Student at University of Beira Interior (Portugal)

Professor at Federal Institute of Education, Science and Technology of Tocantins (Brazil)

http://manoelcampos.com

 about.me

--
If you received an answer that worked for you, please be kind and reply to let everybody knows it worked.
http://cloudsimplus.org
---
You received this message because you are subscribed to the Google Groups "CloudSim Plus: Cloud Simulation Framework" group.
To unsubscribe from this group and stop receiving emails from it, send an email to cloudsimplus...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/cloudsimplus/201efc11-c038-41cb-b93f-293fceb2b56en%40googlegroups.com.

[duaa h]

thank you for replaying... 

I tried to increase cloudlet length gradually, nothing changes until I reach to 500,000 MI, a very little improvement in finished cloudlets is happen. 

But still my problem is not solved. I also tied to decrease  MIPS for VM/Host but that makes simulation takes too long time and also cloudlets did not finished.

[Manoel Campos]

The last time this issue happened, the developer was messing up with the framework code. Try to provide a minimal example that shows the issue

To view this discussion on the web visit https://groups.google.com/d/msgid/cloudsimplus/c7bbd0e8-7d27-4c17-8965-17096e09863an%40googlegroups.com.

--

[duaa h]

I could not  include the issue in a simple example because it is a big program and I think the problem related to many parts of it. 

fortunately, I found the main reason  of the problem . I want to submit one VM to multiple brokers but CloudSim is not allowed that, so I create a new broker and submit all cloudlets of those multiple brokers to him (brokers and cloudlets read from google trace file). This causes a confusion in simulation and leads to un execute most of cloudlets.

Could you help me please if  there is another way to submit one VM to multiple brokers ?

[Manoel Campos]

You cannot send the sabe VMs to multiple brokers. A VM is a unique entity. If you want two VMs with the same configuration to be started, you have to create 2 VM instances with the same config and different IDs and submit each one to the broker you want (the same or distinct brokers).

In real cloud DC, even if you have 2 VMs created from the same image, they are two different instances (with different IDs)

To view this discussion on the web visit https://groups.google.com/d/msgid/cloudsimplus/f21aaf01-b81a-4500-8f04-2398882a97f1n%40googlegroups.com.