aws / aws/amazon-sagemaker-feedback

Preview for cpu and memory on sagemaker studio instances is inaccurate

Open
#183 0 comments 0 reactions 0 assignees View on GitHub
bug
Dominant language
No language data
Stars
10
Forks
3
PR merge metrics
No merged PRs in 30d

Description

### Product Version

- [ ] Amazon SageMaker Studio Classic
- [x] Amazon SageMaker Studio
- [ ] Issue is not related to SageMaker Studio

### Issue Description

First open Sagemaker Studio in GovCloud. Go to JupyterLab. Select "Create JupyterLab Space". The CPU and Memory for any of the ml.g6 family of instances are not accurate. See attached photo. The ml.g6.48xlarge instance does not have 768 CPUs. This is misleading.

### Expected Behavior

The CPU and memory attributes should probably be similar to this website.
https://aws.amazon.com/ec2/instance-types/

### Observed Behavior

Image

### Product Category

JupyterLab

### Feedback Category

User Interface

### Other Details

_No response_

Contributor guide

Open the contributing guide

Research direction

No repository files or tests are identified. Reproduce the issue by opening SageMaker Studio in GovCloud, entering JupyterLab, and selecting Create JupyterLab Space for an ml.g6 instance; compare the displayed CPU and memory values with the AWS EC2 instance-types reference. Done means the preview reports accurate attributes, including for ml.g6.48xlarge.

Written by the indexing model from the issue text.

Assessment

Tech stack
aws
Domain
cloud
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.