Skip to content

[Refactor:Developer] Increase default ram and cpus for speed#12149

Merged
bmcutler merged 3 commits into
mainfrom
beefy-vagrant
Apr 30, 2026
Merged

[Refactor:Developer] Increase default ram and cpus for speed#12149
bmcutler merged 3 commits into
mainfrom
beefy-vagrant

Conversation

@lavalleeale

Copy link
Copy Markdown
Contributor

Why is this Change Important & Necessary?

Developer machines have gotten a lot stronger since some of our defaults were set, and this is causing both bugs that seem to be due to lack of resources and a slower development experience in general.

What is the New Behavior?

The default ram for the vagrant box has been changed from 2GB to 4GB and the cpus have been changed from 2 to 4.

What steps should a reviewer take to reproduce or test the bug or new feature?

  1. Check out this pr
  2. vagrant halt
  3. vagrant up
  4. Check utm/qemu/virtualbox and verify the new specs are in use.

Automated Testing & Documentation

Other information

@codecov

codecov Bot commented Oct 21, 2025

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 21.67%. Comparing base (a198c51) to head (705a08a).
⚠️ Report is 9 commits behind head on main.

Additional details and impacted files

Impacted file tree graph

@@            Coverage Diff            @@
##               main   #12149   +/-   ##
=========================================
  Coverage     21.67%   21.67%           
  Complexity     9807     9807           
=========================================
  Files           268      268           
  Lines         36722    36722           
  Branches        490      490           
=========================================
  Hits           7960     7960           
  Misses        28276    28276           
  Partials        486      486           
Flag Coverage Δ
autograder 21.32% <ø> (ø)
js 2.02% <ø> (ø)
migrator 100.00% <ø> (ø)
php 20.73% <ø> (ø)
python_submitty_utils 80.08% <ø> (ø)
submitty_daemon_jobs 91.13% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

Comment thread Vagrantfile Outdated
VM_MEMORY = ENV.fetch('VM_MEMORY', ON_CI ? '1024' : '2048').to_i
VM_CPUS = ENV.fetch('VM_CPUS', ON_CI ? '1' : '2').to_i
VM_MEMORY = ENV.fetch('VM_MEMORY', ON_CI ? '1024' : '4096').to_i
VM_CPUS = ENV.fetch('VM_CPUS', ON_CI ? '1' : '4').to_i

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.

This will scale poorly if running a worker setup (e.g. 3 workers => 16G of ram + 16 vcpus)
Most dev machines will not be able to handle this.
What issues were the previous specs causing, and are they widespread enough to the point where we need to change the default?

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

I agree that we should change the default. Doing so will make incremental install_submitty runs, initial VM setup, and autograding faster at a minimum.

You do raise a good point about multiple workers though. Can we set a higher limit for the primary VM and keep the current limits for the workers?

@github-project-automation github-project-automation Bot moved this from Seeking Reviewer to Work in Progress in Submitty Development Oct 21, 2025
@github-actions github-actions Bot added the Abandoned PR - Needs New Owner No activity on PR for more than 2 weeks -- seeking new owner to complete label Nov 5, 2025
@hyeenaa hyeenaa self-assigned this Apr 30, 2026
@bmcutler
bmcutler merged commit dc4b908 into main Apr 30, 2026
24 of 25 checks passed
@bmcutler
bmcutler deleted the beefy-vagrant branch April 30, 2026 22:40
@github-project-automation github-project-automation Bot moved this from Work in Progress to Done in Submitty Development Apr 30, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Abandoned PR - Needs New Owner No activity on PR for more than 2 weeks -- seeking new owner to complete

Projects

Archived in project

Development

Successfully merging this pull request may close these issues.

5 participants