Understanding flavors - Revision history

Dtadmin at 16:16, 16 May 2024

2024-05-16T16:16:25Z

← Older revision		Revision as of 16:16, 16 May 2024
Line 1:		Line 1:
	<strong>~~Understanding~~ flavors</strong>		<strong>This article explains the DataTenant cloud compute flavors.</strong>

	'Flavors' in the DataTenant cloud describe the virtual hardware that will be allocated to a virtual machine/instance. For example, a 'small' flavor might mean a virtual machine will have 2 virtual CPUs and 4 GB of virtual RAM. A 'large' flavor might mean a virtual machine will have 8 virtual CPUs and 16 GB of virtual RAM.		'Flavors' in the DataTenant cloud describe the virtual hardware that will be allocated to a virtual machine/instance. For example, a 'small' flavor might mean a virtual machine will have 2 virtual CPUs and 4 GB of virtual RAM. A 'large' flavor might mean a virtual machine will have 8 virtual CPUs and 16 GB of virtual RAM.

Dtadmin at 16:05, 16 May 2024

2024-05-16T16:05:50Z

← Older revision		Revision as of 16:05, 16 May 2024
Line 15:		Line 15:


	In addition, flavors will have a version indicator, like v0, v1, v2, etc. These version numbers correspond to hardware generations in the back-end infrastructure. Higher version numbers indicate new generations of hardware. Higher versions will often (though not always) be more expensive than lower versions.\		In addition, flavors will have a version indicator, like v0, v1, v2, etc. These version numbers correspond to hardware generations in the back-end infrastructure. Higher version numbers indicate new generations of hardware. Higher versions will often (though not always) be more expensive than lower versions.


	For more information on how different flavors affect your costs, please review our [[Pricing]] article.		For more information on how different flavors affect your costs, please review our [[Pricing]] article.

Dtadmin at 16:05, 16 May 2024

2024-05-16T16:05:43Z

← Older revision		Revision as of 16:05, 16 May 2024
Line 15:		Line 15:


	In addition, flavors will have a version indicator, like v0, v1, v2, etc. These version numbers correspond to hardware generations in the back-end infrastructure. Higher version numbers indicate new generations of hardware. Higher versions will often (though not always) be more expensive than lower versions.		In addition, flavors will have a version indicator, like v0, v1, v2, etc. These version numbers correspond to hardware generations in the back-end infrastructure. Higher version numbers indicate new generations of hardware. Higher versions will often (though not always) be more expensive than lower versions.\

	For more information on how different flavors affect your costs, please review our [[Pricing]] article.		For more information on how different flavors affect your costs, please review our [[Pricing]] article.

Dtadmin at 16:05, 16 May 2024

2024-05-16T16:05:06Z

← Older revision		Revision as of 16:05, 16 May 2024
Line 13:		Line 13:

	Choosing a tier that is underneath your instance's needs may result in bad performance during peak periods when the instance requires maximum CPU power allocation. Tiers can be changed at will, however, by following our [[Changing flavors]] article.		Choosing a tier that is underneath your instance's needs may result in bad performance during peak periods when the instance requires maximum CPU power allocation. Tiers can be changed at will, however, by following our [[Changing flavors]] article.


			In addition, flavors will have a version indicator, like v0, v1, v2, etc. These version numbers correspond to hardware generations in the back-end infrastructure. Higher version numbers indicate new generations of hardware. Higher versions will often (though not always) be more expensive than lower versions.

			For more information on how different flavors affect your costs, please review our [[Pricing]] article.

Dtadmin at 16:02, 16 May 2024

2024-05-16T16:02:16Z

← Older revision		Revision as of 16:02, 16 May 2024
Line 8:		Line 8:
	* <span style="color:blue">Blue Tier</span>: Your instance will mostly sit idle but will need occasionally to burst to high levels of CPU consumption. This is the least expensive tier.		* <span style="color:blue">Blue Tier</span>: Your instance will mostly sit idle but will need occasionally to burst to high levels of CPU consumption. This is the least expensive tier.

	* <span style="color:yellow;background-color:~~black~~">Yellow Tier</span>: Your instance will sit idle for part of the day but will burst to high levels of CPU for prolonged periods of the day. This is the middle tier in terms of cost.		* <span style="color:yellow;background-color:grey">Yellow Tier</span>: Your instance will sit idle for part of the day but will burst to high levels of CPU for prolonged periods of the day. This is the middle tier in terms of cost.

	* <span style="color:red">Red Tier</span>: Your instance will using most or all of its allocated CPU power for the majority of the day. This is the most expensive tier.		* <span style="color:red">Red Tier</span>: Your instance will using most or all of its allocated CPU power for the majority of the day. This is the most expensive tier.

	Choosing a tier that is underneath your instance's needs may result in bad performance during peak periods when the instance requires maximum CPU power allocation. Tiers can be changed at will, however, by following our [[Changing flavors]] article.		Choosing a tier that is underneath your instance's needs may result in bad performance during peak periods when the instance requires maximum CPU power allocation. Tiers can be changed at will, however, by following our [[Changing flavors]] article.

Dtadmin at 16:01, 16 May 2024

2024-05-16T16:01:58Z

← Older revision		Revision as of 16:01, 16 May 2024
Line 8:		Line 8:
	* <span style="color:blue">Blue Tier</span>: Your instance will mostly sit idle but will need occasionally to burst to high levels of CPU consumption. This is the least expensive tier.		* <span style="color:blue">Blue Tier</span>: Your instance will mostly sit idle but will need occasionally to burst to high levels of CPU consumption. This is the least expensive tier.

	* <span style="color:yellow"; background-color: black>Yellow Tier</span>: Your instance will sit idle for part of the day but will burst to high levels of CPU for prolonged periods of the day. This is the middle tier in terms of cost.		* <span style="color:yellow;background-color:black">Yellow Tier</span>: Your instance will sit idle for part of the day but will burst to high levels of CPU for prolonged periods of the day. This is the middle tier in terms of cost.

	* <span style="color:red">Red Tier</span>: Your instance will using most or all of its allocated CPU power for the majority of the day. This is the most expensive tier.		* <span style="color:red">Red Tier</span>: Your instance will using most or all of its allocated CPU power for the majority of the day. This is the most expensive tier.

	Choosing a tier that is underneath your instance's needs may result in bad performance during peak periods when the instance requires maximum CPU power allocation. Tiers can be changed at will, however, by following our [[Changing flavors]] article.		Choosing a tier that is underneath your instance's needs may result in bad performance during peak periods when the instance requires maximum CPU power allocation. Tiers can be changed at will, however, by following our [[Changing flavors]] article.

Dtadmin at 16:01, 16 May 2024

2024-05-16T16:01:40Z

← Older revision		Revision as of 16:01, 16 May 2024
Line 8:		Line 8:
	* <span style="color:blue">Blue Tier</span>: Your instance will mostly sit idle but will need occasionally to burst to high levels of CPU consumption. This is the least expensive tier.		* <span style="color:blue">Blue Tier</span>: Your instance will mostly sit idle but will need occasionally to burst to high levels of CPU consumption. This is the least expensive tier.

	* <span style="color:yellow">Yellow Tier</span>: Your instance will sit idle for part of the day but will burst to high levels of CPU for prolonged periods of the day. This is the middle tier in terms of cost.		* <span style="color:yellow"; background-color: black>Yellow Tier</span>: Your instance will sit idle for part of the day but will burst to high levels of CPU for prolonged periods of the day. This is the middle tier in terms of cost.

	* <span style="color:red">Red Tier</span>: Your instance will using most or all of its allocated CPU power for the majority of the day. This is the most expensive tier.		* <span style="color:red">Red Tier</span>: Your instance will using most or all of its allocated CPU power for the majority of the day. This is the most expensive tier.

	Choosing a tier that is underneath your instance's needs may result in bad performance during peak periods when the instance requires maximum CPU power allocation. Tiers can be changed at will, however, by following our [[Changing flavors]] article.		Choosing a tier that is underneath your instance's needs may result in bad performance during peak periods when the instance requires maximum CPU power allocation. Tiers can be changed at will, however, by following our [[Changing flavors]] article.

Dtadmin at 16:00, 16 May 2024

2024-05-16T16:00:55Z

← Older revision		Revision as of 16:00, 16 May 2024
Line 6:		Line 6:
	In the DataTenant cloud, each flavor 'size' is also broken out by tier and version. Our three tiers are 'blue', 'yellow', and 'red'. You should choose your tier based on how often you feel your instance CPU will need to the majority of its available processing power:		In the DataTenant cloud, each flavor 'size' is also broken out by tier and version. Our three tiers are 'blue', 'yellow', and 'red'. You should choose your tier based on how often you feel your instance CPU will need to the majority of its available processing power:

	* Blue Tier: Your instance will mostly sit idle but will need occasionally to burst to high levels of CPU consumption. This is the least expensive tier.		* <span style="color:blue">Blue Tier</span>: Your instance will mostly sit idle but will need occasionally to burst to high levels of CPU consumption. This is the least expensive tier.

	* Yellow Tier: Your instance will sit idle for part of the day but will burst to high levels of CPU for prolonged periods of the day. This is the middle tier in terms of cost.		* <span style="color:yellow">Yellow Tier</span>: Your instance will sit idle for part of the day but will burst to high levels of CPU for prolonged periods of the day. This is the middle tier in terms of cost.

	* <span style="color:red">Red Tier</span>: Your instance will using most or all of its allocated CPU power for the majority of the day. This is the most expensive tier.		* <span style="color:red">Red Tier</span>: Your instance will using most or all of its allocated CPU power for the majority of the day. This is the most expensive tier.

	Choosing a tier that is underneath your instance's needs may result in bad performance during peak periods when the instance requires maximum CPU power allocation. Tiers can be changed at will, however, by following our [[Changing flavors]] article.		Choosing a tier that is underneath your instance's needs may result in bad performance during peak periods when the instance requires maximum CPU power allocation. Tiers can be changed at will, however, by following our [[Changing flavors]] article.

Dtadmin: Created page with "Understanding flavors 'Flavors' in the DataTenant cloud describe the virtual hardware that will be allocated to a virtual machine/instance. For example, a 'small' flavor might mean a virtual machine will have 2 virtual CPUs and 4 GB of virtual RAM. A 'large' flavor might mean a virtual machine will have 8 virtual CPUs and 16 GB of virtual RAM. == Understanding flavor tiers and versions == In the DataTenant cloud, each flavor 'size' is also broken out b..."

2024-05-16T16:00:16Z

Created page with "Understanding flavors 'Flavors' in the DataTenant cloud describe the virtual hardware that will be allocated to a virtual machine/instance. For example, a 'small' flavor might mean a virtual machine will have 2 virtual CPUs and 4 GB of virtual RAM. A 'large' flavor might mean a virtual machine will have 8 virtual CPUs and 16 GB of virtual RAM. == Understanding flavor tiers and versions == In the DataTenant cloud, each flavor 'size' is also broken out b..."

New page

Understanding flavors

'Flavors' in the DataTenant cloud describe the virtual hardware that will be allocated to a virtual machine/instance. For example, a 'small' flavor might mean a virtual machine will have 2 virtual CPUs and 4 GB of virtual RAM. A 'large' flavor might mean a virtual machine will have 8 virtual CPUs and 16 GB of virtual RAM.

== Understanding flavor tiers and versions ==
In the DataTenant cloud, each flavor 'size' is also broken out by tier and version. Our three tiers are 'blue', 'yellow', and 'red'. You should choose your tier based on how often you feel your instance CPU will need to the majority of its available processing power:

* Blue Tier: Your instance will mostly sit idle but will need occasionally to burst to high levels of CPU consumption. This is the least expensive tier.

* Yellow Tier: Your instance will sit idle for part of the day but will burst to high levels of CPU for prolonged periods of the day. This is the middle tier in terms of cost.

* Red Tier: Your instance will using most or all of its allocated CPU power for the majority of the day. This is the most expensive tier.

Choosing a tier that is underneath your instance's needs may result in bad performance during peak periods when the instance requires maximum CPU power allocation. Tiers can be changed at will, however, by following our [[Changing flavors]] article.