Description: In cloud computing, VMSchedulerSpaceShared and VMSchedulerTimeShared are VM scheduling policies used in cloud simulators like CloudSim to allocate virtual machines (VMs) to physical resources (hosts) in a data center. These policies define how VMs share the physical resources (like CPU cores or processing elements) of a host.
VM Scheduler Space Shared
Description: The VM Scheduler Space Shared policy allocates a VM to a host in such a way that multiple VMs share the same physical resources (CPU cores) of the host. Each VM will receive a fraction of the available physical resources. This means that the VMs are co-located on the same processing elements but do not receive exclusive access to them.
How It Works: In this policy, VMs can share the same CPU core. This is typically used when there are many VMs that need to be allocated to a host with limited processing resources. The system doesn't restrict the number of VMs on a given host; instead, it divides available resources among them.
Example: In environments where numerous small, low-intensity applications are running simultaneously.
VM Scheduler Space Shared
Description: The VM Scheduler Time Shared policy allocates CPU resources to VMs based on time-sharing. In this model, each VM gets a slice of CPU time on the host, and they switch between VMs in a round-robin or time-sliced manner. This allows multiple VMs to share the same CPU core, but each gets its turn to execute on the core.
How It Works: Each VM is allocated CPU time in discrete time slots, where the VM executes for a fixed duration before the next VM gets a turn. The scheduling happens on a time-sharing basis, meaning that CPU resources are divided based on time, not space. This policy is used when the VMs are not resource-intensive and do not need continuous access to the CPU. Instead, the VMs share CPU time to optimize resource usage.
Example: Used for general-purpose cloud computing platforms where multiple VMs need CPU access but are not running heavy computational tasks simultaneously.
Research Breakthrough Possible @S-Logix
