Merge pull request #298298 from craigshoemaker/patch-11

[Container Apps] Update: cold-start.md -> add note for serverless GPUs for artifact streaming

Author: prmerger-automator[bot]

articles/container-apps/cold-start.md

@@ -5,7 +5,7 @@ services: container-apps
 author: craigshoemaker
 ms.service: azure-container-apps
 ms.topic: conceptual
-ms.date: 03/20/2025
+ms.date: 04/15/2025
 ms.author: cshoe
 ---
 
@@ -31,6 +31,9 @@ Use container registries close to your Container Apps environment. Usually this
 
 Azure Container Registry [offers image streaming](/azure/container-apps/serverless-gpu-nim#enable-artifact-streaming-recommended-but-optional) which can speed up image startup by up to 15%.
 
+> [!NOTE]
+> Artifact streaming is only supported with [serverless GPUs](./gpu-serverless-overview.md).
+
 ## Implement custom liveness health probe or start listening early
 
 Azure Container Apps automatically sets up a [liveness probe](health-probes.md) when ingress is enabled. Images and applications take a long time to start after the image is launched can cause issues with the container. Container Apps could kill the starting application because it fails the liveness probe.
@@ -50,4 +53,4 @@ For troubleshooting performance issues, implement application-side performance m
 ## Proactively wake your app
 
 If the above recommendations don’t provide the desired performance, wake your app ahead of any actual usage. For example, consider setting up a job at 9am to wake the application ahead of employees starting their work day. This approach could eliminate lengthy cold-starts while still allowing for scale-to-zero cost-savings whenever the app isn't in use.
- 
+