가상 머신(VM) 인스턴스의 테넌시는 VM이 다른 Google Cloud 프로젝트의 VM과 Compute Engine 서버를 공유하는지 여부를 나타냅니다. VM이 Compute Engine 서버를 다른Google Cloud 프로젝트의 VM과 공유하는 경우 해당 VM은 멀티 테넌트 VM입니다. VM이 Compute Engine 서버를 다른 프로젝트의 VM과 공유하지 않는 경우 해당 VM은 단독 테넌트 VM입니다.
VM은 기본적으로 멀티 테넌트입니다. 사용자가 VM을 만들면 Compute Engine이 VM을 멀티 테넌트 서버에 배치합니다. Compute Engine을 사용하면 다른 Google Cloud 프로젝트의 사용자가 해당 서버에 VM을 만들 수 있습니다.
단독 테넌시는 Compute Engine 서버에 독점적으로 액세스해야 하는 워크로드에 적합합니다. 단독 테넌시를 사용하면Google Cloud 프로젝트에서만 VM을 호스팅하는 Compute Engine 서버인 단독 테넌트 노드에 독점적으로 액세스할 수 있습니다.
가격 책정 고려사항
멀티 테넌트 VM의 경우 VM을 생성하는 머신 유형에 따라 요금이 부과되므로 멀티 테넌트 VM의 가격 책정은 해당 VM의 머신 계열을 기반으로 합니다.
단독 테넌트 VM의 경우 전체 물리적 서버를 예약하므로 서버의 모든 하드웨어 리소스에 대한 비용을 지불해야 합니다. 단독 테넌트 노드 가격 책정은 단독 테넌트 노드 템플릿을 만들 때 지정하는 단독 테넌트 노드 유형의 가격을 기반으로 합니다. 이 가격은 전체 물리적 서버를 예약하므로 프리미엄을 포함합니다.
[[["이해하기 쉬움","easyToUnderstand","thumb-up"],["문제가 해결됨","solvedMyProblem","thumb-up"],["기타","otherUp","thumb-up"]],[["이해하기 어려움","hardToUnderstand","thumb-down"],["잘못된 정보 또는 샘플 코드","incorrectInformationOrSampleCode","thumb-down"],["필요한 정보/샘플이 없음","missingTheInformationSamplesINeed","thumb-down"],["번역 문제","translationIssue","thumb-down"],["기타","otherDown","thumb-down"]],["최종 업데이트: 2025-09-03(UTC)"],[[["\u003cp\u003eVirtual machines (VMs) can be either multi-tenant, sharing a server with other Google Cloud projects' VMs, or sole-tenant, having exclusive use of a server.\u003c/p\u003e\n"],["\u003cp\u003eMulti-tenant VMs are the default, suitable for typical workloads, and their pricing is based on the machine type, while sole-tenant VMs are more expensive as the entire physical server is reserved.\u003c/p\u003e\n"],["\u003cp\u003eSole-tenancy is recommended for workloads with specific performance, security, compliance, or licensing needs, such as gaming, finance, healthcare, Windows, machine learning, and workloads requiring increased input/output operations per second (IOPS).\u003c/p\u003e\n"],["\u003cp\u003eMaintenance events on multi-tenant servers result in live migration of VMs, while sole-tenant server maintenance depends on the configured maintenance policy.\u003c/p\u003e\n"],["\u003cp\u003eUsers pay based on machine type for Multi-tenant VMs, and for sole-tenant nodes it is based on the node type, which includes a premium because you are reserving the entire physical server.\u003c/p\u003e\n"]]],[],null,["Linux Windows\n\n*** ** * ** ***\n\nThe *tenancy* of a virtual machine (VM) instance indicates whether the VM shares\nits Compute Engine server with VMs from other Google Cloud projects. If a VM\nshares its Compute Engine server with VMs from other\nGoogle Cloud projects, it is a *multi-tenant* VM. If a VM doesn't share its\nCompute Engine server with VMs from other projects, it is a\n*sole-tenant* VM.\n\nVMs are multi-tenant by default. After you create a VM, Compute Engine\nplaces it on a multi-tenant server. Compute Engine allows users in\nother\n[Google Cloud projects](/resource-manager/docs/creating-managing-projects)\nto create VMs on that server.\n\n[Sole-tenancy](/compute/docs/nodes/sole-tenant-nodes) is suited for workloads\nthat require exclusive access to a Compute Engine server. Sole-tenancy\nlets you have exclusive access to a *sole-tenant node*, which is a\nCompute Engine server that is dedicated to hosting VMs from only your\nGoogle Cloud projects.\n\nPricing considerations\n\nFor multi-tenant VMs, you pay for the type of machine that you create the VM on,\nso [pricing for multi-tenant VMs](/compute/vm-instance-pricing) is based on that\nVM's [machine family](/compute/docs/machine-resource).\n\nFor sole-tenant VMs, you pay for all of the hardware resources on the server\nbecause you are reserving an entire physical server. [Pricing for a sole-tenant\nnode](/compute/sole-tenant-pricing) is based on the price of the [sole-tenant\nnode type](/compute/docs/nodes/sole-tenant-nodes#node_types) that you specify\nwhen you create a [sole-tenant node\ntemplate](/compute/docs/nodes/sole-tenant-nodes#node_templates). This price\nincludes a premium because you are reserving the entire physical server.\n\nWorkload considerations\n\nFor typical workloads, [create multi-tenant\nVMs](/compute/docs/instances/create-start-instance). However, if you have\nworkloads with any of the following characteristics, consider [using sole-tenant\nnodes](/compute/docs/nodes/provisioning-sole-tenant-vms):\n\n- Gaming workloads with specific computing performance requirements.\n- Finance or healthcare workloads with security and compliance requirements.\n- Windows workloads with licensing requirements.\n- Machine learning, data processing, or image rendering workloads. For these workloads, consider [reserving GPUs](/compute/docs/nodes/provisioning-sole-tenant-vms).\n- Workloads requiring increased input/output operations per second (IOPS) and decreased latency, or workloads that use temporary storage in the form of caches, processing space, or low-value data. For these workloads, consider [reserving Local SSDs](/compute/docs/nodes/provisioning-sole-tenant-vms).\n\nFor more information about workloads that might benefit from using sole-tenancy,\nsee [Workload considerations for sole-tenant\nnodes](/compute/docs/nodes/sole-tenant-nodes#workload_considerations).\n\nMaintenance event considerations\n\nFor maintenance events on multi-tenant servers, Compute Engine [live\nmigrates](/compute/docs/instances/live-migration-process) VMs to another server in the\nsame zone.\n\nFor maintenance events on sole-tenant nodes, Compute Engine migrates\nVMs according to how you configure the [maintenance\npolicy](/compute/docs/nodes/sole-tenant-nodes#maintenance_policies) on the\n[sole-tenant node\ngroup](/compute/docs/nodes/sole-tenant-nodes#node_groups_and_vm_provisioning)."]]
