Skip to content
This repository was archived by the owner on Apr 23, 2026. It is now read-only.

chore: Increase medium e2e instance size to g6.16xlarge - #3301

Closed
courtneypacheco wants to merge 1 commit into
mainfrom
increase-medium-ec2-instance-size
Closed

chore: Increase medium e2e instance size to g6.16xlarge#3301
courtneypacheco wants to merge 1 commit into
mainfrom
increase-medium-ec2-instance-size

Conversation

@courtneypacheco

Copy link
Copy Markdown
Contributor

Checklist:

  • Commit Message Formatting: Commit titles and messages follow guidelines in the
    conventional commits.
  • Changelog updated with breaking and/or notable changes for the next minor release.
  • Documentation has been updated, if necessary.
  • Unit tests have been added, if necessary.
  • Functional tests have been added, if necessary.
  • E2E Workflow tests have been added, if necessary.

Signed-off-by: Courtney Pacheco <6019922+courtneypacheco@users.noreply.github.com>
@mergify mergify Bot added the CI/CD Affects CI/CD configuration label Apr 18, 2025
github-token: ${{ secrets.GH_PERSONAL_ACCESS_TOKEN }}
ec2-image-id: ${{ vars.AWS_EC2_AMI }}
ec2-instance-type: g6.8xlarge
ec2-instance-type: g6.16xlarge

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

at the very least put a comment to revert it later; and link to #3298

That said, I don't think we should use bumps without first trying to collect some disk usage data on the node. I doubt the size of the disk is the actual problem with gguf writer. Having some monitoring / stats collection during job run that we could then dump to github logs and inspect would help here.

github-token: ${{ secrets.GH_PERSONAL_ACCESS_TOKEN }}
ec2-image-id: ${{ vars.AWS_EC2_AMI }}
ec2-instance-type: g6.8xlarge
ec2-instance-type: g6.16xlarge

@danmcp danmcp Apr 18, 2025

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What's the intention of this change?

I assume it's to get more RAM for a larger tmp by default?

@danmcp danmcp mentioned this pull request Apr 18, 2025
6 tasks
@nathan-weinberg

Copy link
Copy Markdown
Contributor

No context? Are we spending money just for the sake of spending money? 😉

@booxter

booxter commented May 14, 2025

Copy link
Copy Markdown
Contributor

I believe this is not relevant anymore. Feel free to reopen if needed.

@booxter booxter closed this May 14, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

CI/CD Affects CI/CD configuration

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants