Notes on Time shared VM scheduling and time shared Cloudlet scheduling.

So I got the simulation results, but nothing seems to be happening.
All the cloudlets start at 19.6 units of time.... i am assuming after all the cloudlets have been scheduled...
So now if we take a closer look...
I segregated the scheduling of cloudlets by VM... so sample output for VM#0 is given below.

<br /> cloudlet STATUS Data VM ID Submit Run Start Finish Response time<br /> ID centerID time time time time <br /> 9751 SUCCESS 2 0 3 0.93 22.6 23.53 19.6<br /> 341 SUCCESS 2 0 4 0.83 23.6 24.44 19.6<br /> 21 SUCCESS 2 0 2 3.51 21.6 25.11 19.6<br /> 1 SUCCESS 2 0 2 4.06 21.6 25.66 19.6<br /> 551 SUCCESS 2 0 5 1.3 24.6 25.9 19.6<br /> 9981 SUCCESS 2 0 2 4.88 21.6 26.48 19.6<br /> 581 SUCCESS 2 0 5 2.27 24.6 26.87 19.6<br /> 9241 SUCCESS 2 0 7 2.13 26.6 28.73 19.6<br /> 9171 SUCCESS 2 0 8 2.47 27.6 30.08 19.6<br /> 9731 SUCCESS 2 0 3 9.35 22.6 31.95 19.6<br /> <br />

If I use the formula, for Response time as start time - submit time.... I'm getting 19.6 for all the cloudlets...
and also if i see cloudlet ID 21 and 1, 9981, they all start at the same time...
(After looking at the concepts more thoroughly,  in time shared cloudlets and VM's, multiple cloudlets can multitask within a Vm )
I've specified VM Utilization Full.

Looking at the definition once more we see...

Allocation of VM's to the host

VmAllocationPolicy is an abstract class that represents the provisioning policy of hosts to virtual machines in a Datacentre. It supports two-stage commit of reservation of hosts: first, we reserve the host and, once commited by the user, it is effectively allocated to he/she.
And from this class, we use:
VmAllocationPolicySimple is an VmAllocationPolicy that chooses, as the host for a VM, the host with less PEs in use.

Resource usage by cloudlet

The UtilizationModel interface needs to be implemented in order to provide a fine-grained control over resource usage by a Cloudlet.

And from this interface we use:
The UtilizationModelFull class is a simple model, according to which a Cloudlet always utilize all the available CPU capacity.

Policy for cloudlet scheduling

CloudletScheduler is an abstract class that represents the policy of scheduling performed by a virtual machine. So, classes extending this must execute Cloudlets. Also, the interface for cloudlet management is also implemented in this class.
In this we use

CloudletSchedulerTimeShared implements a policy of scheduling performed by a virtual machine. Cloudlets execute time-shared in VM. 

Policy for VM scheduling

VmScheduler is an abstract class that represents the policy used by a VMM to share processing power among VMs running in a host. 
The policy we are using is
VmSchedulerTimeShared is a VMM allocation policy that allocates one or more Pe to a VM, and allows sharing of PEs by multiple VMs. This class also implements 10% performance degration due to VM migration. This scheduler does not support over-subscription. 

The model we are using is
Time shared for VM's and tasks

 

Note ** In time shared mode, multiple cloudlets ( task units ) can simultaeneously multitask within a Vm.

Why?
I can understand now if cloudlets have the same start time... but in a time shared environment, context switching takes place, so the finish time for the cloudlet should be more than the actual run time...
will check that now...