기술 자료

​
​

Development

User Acquisition

Monetization

산업 분야

Self-Hosted Deployment

Amazon Web Services

Microsoft Azure

On premises

vpctl

Self-Hosted Deployment

이 페이지는 선택한 언어로 제공되지 않습니다.
​
​
Self-Hosted Deployment
  • Overview
  • Amazon Web Services
  • Microsoft Azure
  • On premises
    • Release notes
    • Installation
      • Infrastructure overview
      • Hardware requirements
      • Prerequisites
      • Deployment
      • Postdeployment
      • Costs
    • Maintenance
  • Administration
  • Security
  • vpctl
  1. Self-Hosted Deployment (previously called Unity Virtual Private Cloud)
  2. Self-Hosted Deployment on-premises
  3. Installation

Hardware requirements

Plan the physical infrastructure for a baseline production on-premises deployment
읽는 시간 2분
최근 업데이트: 한 달 전

Use this page to estimate the physical hardware for a baseline production on-premises deployment. Actual sizing depends on user volume, workload concurrency, transformation complexity, storage footprint, and your availability requirements.
참고
This page applies to customers who supply their own physical or datacenter hardware. If you deploy to an existing managed Kubernetes platform, use the Kubernetes resource profiles on Overview of the infrastructure to determine sizing. The profiles (small, medium, large) specify Kubernetes resource allocations rather than physical hardware. Use the medium profile for production by default.

Typical infrastructure profile

A baseline production deployment requires approximately the following capacity:
  • 88 vCPUs
  • 400 GB RAM
  • Supporting database, storage, observability, and internal platform services

Recommended hardware for production

For production, high availability, and spare capacity, provision the following hardware:

Item

Description

Compute serversThree enterprise rack servers, each with 24–32 cores and 256 GB RAM
Storage8–12 TB enterprise NVMe or all-flash usable capacity
Networking10/25 GbE switching, firewall, and cabling
Backup and disaster recoveryBackup appliance or backup integration
UPS and power protectionRack UPS and related power equipment
Optional GPUNVIDIA L4 or equivalent,, where transformation workload requires it

Sizing variables

Adjust the hardware profile based on the following factors:
  • User volume: the number of concurrent users who access Unity Asset Manager
  • Workload concurrency: the number of simultaneous transformations and operations
  • Transformation licensing: the number of concurrent transformations your Unity Asset Transformer SDK license permits; licensing can limit throughput independently of GPU and CPU capacity
  • Transformation complexity: the size and complexity of the 3D assets you transform
  • Storage footprint: the total volume of assets you store on the platform
  • Availability requirements: your high availability targets and redundancy needs

Copyright © 2026 Unity Technologies
법률 정보개인정보 처리방침쿠키Documentation Terms of Use개인 정보 판매 또는 공유 금지개인정보 보호 선택(쿠키 설정)

'Unity', Unity 로고 및 기타 Unity 상표는 미국 및 기타 지역 내 Unity Technologies 또는 그 계열사의 상표 또는 등록상표입니다(자세한 내용은 여기에서 확인하세요). 기타 명칭 또는 브랜드는 해당 소유자의 상표입니다.

일부 페이지는 편의를 위해 기계 번역되었으며 부정확한 내용이 있을 수 있습니다. 정보가 상충되는 경우, 영어 버전을 우선으로 참조하세요.

  • 보고 있는 페이지
    • Typical infrastructure profile

    • Recommended hardware for production

    • Sizing variables

  • 추가 리소스
  • Overview of the infrastructure
  • Prerequisites
  • Costs

이 페이지의 문제 보고