You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/dev-box/concept-dev-box-serverless-gpu.md
+20-18Lines changed: 20 additions & 18 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -13,18 +13,18 @@ ai-usage: ai-generated
13
13
14
14
# Serverless GPU compute in Microsoft Dev Box
15
15
16
-
Microsoft Dev Box serverless GPU compute enables developers to access powerful GPU resources on demand without requiring permanent infrastructure provisioning or complex setup. This article explains what serverless GPU compute is, how it works, and key scenarios for its use.
16
+
Serverless GPU compute in Microsoft Dev Box lets you use GPU resources on demand for compute-intensive tasks like AI model training, inference, and data processing. Microsoft Dev Box serverless GPU compute enables developers to access powerful GPU resources on demand without requiring permanent infrastructure provisioning or complex setup. This article explains what serverless GPU compute is, how it works, and key scenarios for its use.
17
17
18
18
## What is serverless GPU compute?
19
19
20
-
Serverless GPU compute in Microsoft Dev Box provides on-demand access to GPU resources for compute-intensive workloads like AI model training, inference, and data processing. Unlike traditional GPU provisioning that requires long-term commitments and upfront investments, serverless GPU compute allows you to:
20
+
Serverless GPU compute in Microsoft Dev Box provides on-demand access to GPU resources for compute-intensive workloads like AI model training, inference, and data processing. Unlike traditional GPU provisioning that requires long-term commitments and upfront investments, serverless GPU compute lets you:
21
21
22
22
- Access GPU resources only when needed
23
23
- Scale GPU resources according to workload demands
24
24
- Pay only for actual GPU usage
25
25
- Work within your organization's secure network environment
26
26
27
-
This capability integrates Microsoft Dev Box with Azure Container Apps to deliver GPU power without requiring developers to create or manage the underlying infrastructure.
27
+
This capability integrates Microsoft Dev Box with Azure Container Apps to deliver GPU power without requiring developers to manage infrastructure.
28
28
29
29
## When to use serverless GPU compute
30
30
@@ -38,39 +38,42 @@ Consider using serverless GPU compute in Dev Box for scenarios like:
38
38
39
39
## Key benefits
40
40
41
+
Serverless GPU compute in Microsoft Dev Box offers distinct benefits for both developers and organizations, making it easier to harness GPU power efficiently and securely.
42
+
41
43
### For developers
42
44
43
45
-**No setup required**: Access GPU compute with a single click from your Dev Box environment
46
+
- Access GPU compute with one step from your Dev Box environment.
44
47
-**No permission barriers**: Use GPU resources without needing rights to create cloud infrastructure
45
48
-**Integrated development experience**: Seamlessly use GPU compute within familiar tools like Windows Terminal, Visual Studio, and VS Code
46
-
-**Zero configuration**: GPU sessions start automatically when needed and shut down when not in use
49
+
-**Zero configuration**: GPU sessions start automatically when needed and stop when not in use
47
50
48
51
### For organizations
49
52
50
-
-**Cost optimization**: Pay only for actual GPU usage rather than provisioning dedicated hardware
53
+
-**Cost optimization**: Pay only for the GPU resources you use instead of provisioning dedicated hardware.
51
54
-**Centralized control**: Manage GPU access through project-level policies
52
-
-**Security and compliance**: Keep sensitive data within your secure corporate network while using GPU resources
55
+
-**Security and compliance**: Keep sensitive data in your secure corporate network while using GPU resources
53
56
-**Simplified resource management**: Control GPU usage limits at the project level
54
57
55
58
## How serverless GPU compute works
56
59
57
-
Serverless GPU compute in Dev Box uses Azure Container Apps (ACA) to provide GPU resources on demand. When a developer launches a GPU-enabled shell or tool, Dev Box automatically:
60
+
Serverless GPU compute in Dev Box uses Azure Container Apps (ACA) to provide GPU resources on demand. When a developer starts a GPU-enabled shell or tool, Dev Box automatically:
58
61
59
-
1. Creates a connection to a serverless GPU session
60
-
2. Provisions the necessary GPU resources
61
-
3. Makes those resources available through the developer's terminal or integrated development environment
62
-
4. Automatically terminates the session when no longer needed
62
+
- Creates a connection to a serverless GPU session
63
+
- Provisions the necessary GPU resources
64
+
- Makes those resources available through the developer's terminal or integrated development environment
65
+
- Automatically terminates the session when no longer needed
63
66
64
67
### Available GPU types
65
68
66
-
The following GPU options are currently supported:
69
+
These GPU options are supported:
67
70
68
71
-**NVIDIA T4 GPUs**: Readily available with minimal quota concerns
69
72
-**NVIDIA A100 GPUs**: More powerful but available in limited capacity
70
73
71
74
### Regional availability
72
75
73
-
Currently, GPU resources are available in the following Azure regions:
76
+
GPU resources are available in these Azure regions:
74
77
75
78
- West US 3
76
79
- Sweden North
@@ -82,6 +85,8 @@ Additional regions may be supported in the future based on demand.
82
85
83
86
vNet injection allows customers to integrate their network and security protocols with the serverless GPU environment. While not required for the proof of concept (POC), this feature will be prioritized for public previews and general availability (GA). With vNet injection, customers can achieve tighter control over network and security configurations.
84
87
88
+
vNet injection lets customers control network and security configurations more tightly.
89
+
85
90
### MOBO architecture model
86
91
87
92
Serverless GPU compute adopts the MOBO architecture model for ACA integration. In this model, ACA instances are created and managed within the customer’s subscription, providing a more controlled and streamlined management experience. This ensures that the Dev Box service can securely manage ACA sessions without introducing additional complexity.
@@ -98,18 +103,15 @@ The goal is to provide a seamless, native experience where GPU resources are acc
98
103
99
104
## Administration and management
100
105
101
-
Administrators control serverless GPU access at the project level through Dev Center. Key management capabilities include:
106
+
Admins control serverless GPU access at the project level through Dev Center. Key management capabilities include:
102
107
103
108
-**Enable/disable GPU access**: Control whether projects can use serverless GPU resources
104
109
-**Set concurrent GPU limits**: Specify the maximum number of GPUs that can be used simultaneously across a project
105
110
-**Cost controls**: Manage GPU usage within subscription quotas
106
111
107
112
Access to serverless GPU resources is managed through project-level properties. When the serverless GPU feature is enabled for a project, all Dev Boxes within that project automatically gain access to GPU compute. This simplifies the access model by removing the need for custom roles or pool-based configurations.
108
113
109
-
Future iterations of the project policy infrastructure will provide even more granular control over GPU access and usage.
110
-
111
114
## Related content
112
115
113
-
-[Get started with serverless GPU in Dev Box (link to be added)]
114
-
-[Configure serverless GPU settings in Dev Center (link to be added)]
116
+
-[Blog post](link to be added)
115
117
-[Learn more about Azure Container Apps serverless GPU](/azure/container-apps/sessions-code-interpreter)
0 commit comments