vastai-migration-deep-dive

Solid

Migrate GPU workloads to or from Vast.ai, or between GPU providers. Use when switching from AWS/GCP/Azure GPU instances to Vast.ai, migrating between GPU types, or re-platforming ML infrastructure. Trigger with phrases like "migrate to vastai", "vastai migration", "switch to vastai", "vastai from aws", "vastai from lambda".

AI & Automation 2,266 stars 315 forks Updated today MIT

Install

View on GitHub

Quality Score: 99/100

Stars 20%
100
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# Vast.ai Migration Deep Dive ## Current State !`vastai --version 2>/dev/null || echo 'vastai CLI not installed'` !`pip show vastai 2>/dev/null | grep Version || echo 'N/A'` ## Overview Migrate GPU workloads to Vast.ai from hyperscaler providers (AWS, GCP, Azure) or other GPU clouds (Lambda, RunPod, CoreWeave). Also covers migrating between GPU types on Vast.ai and the reverse migration away from Vast.ai. ## Prerequisites - Existing GPU workload with Docker image - Understanding of current GPU costs and utilization - Checkpoint-based training pipeline (for training migrations) ## Instructions ### Step 1: Cost Comparison Analysis ```python # Compare your current GPU costs against Vast.ai marketplace prices PROVIDER_COSTS = { "aws_p4d.24xlarge": {"gpu": "A100 40GB", "gpus": 8, "hourly": 32.77}, "aws_p3.2xlarge": {"gpu": "V100 16GB", "gpus": 1, "hourly": 3.06}, "gcp_a2-highgpu-1g": {"gpu": "A100 40GB", "gpus": 1, "hourly": 3.67}, "azure_NC24ads_A100_v4": {"gpu": "A100 80GB", "gpus": 1, "hourly": 3.67}, "lambda_1xA100": {"gpu": "A100", "gpus": 1, "hourly": 1.25}, } VASTAI_TYPICAL = { "RTX_4090": 0.20, "A100": 1.50, "H100_SXM": 3.00, } def savings_analysis(current_provider, current_hourly, vastai_gpu, vastai_hourly): monthly_current = current_hourly * 730 # hours/month monthly_vastai = vastai_hourly * 730 savings = monthly_current - monthly_vastai pct = (savings / monthly_current) * 100 ...

Details

Author
jeremylongshore
Repository
jeremylongshore/claude-code-plugins-plus-skills
Created
7 months ago
Last Updated
today
Language
Python
License
MIT

Integrates with

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Solid

vastai-cost-tuning

Optimize Vast.ai GPU cloud costs through smart instance selection and lifecycle management. Use when analyzing GPU spending, reducing training costs, or implementing budget controls for Vast.ai workloads. Trigger with phrases like "vastai cost", "vastai billing", "reduce vastai costs", "vastai pricing", "vastai budget".

2,266 Updated today
jeremylongshore
AI & Automation Solid

vastai-upgrade-migration

Upgrade Vast.ai CLI, migrate API versions, and handle breaking changes. Use when upgrading vastai CLI, detecting deprecations, or migrating between API versions. Trigger with phrases like "upgrade vastai", "vastai migration", "vastai breaking changes", "update vastai CLI".

2,266 Updated today
jeremylongshore
AI & Automation Solid

vastai-performance-tuning

Optimize Vast.ai GPU instance selection, startup time, and training throughput. Use when optimizing instance selection, reducing startup latency, or maximizing GPU utilization on rented hardware. Trigger with phrases like "vastai performance", "optimize vastai", "vastai slow", "vastai gpu utilization", "vastai throughput".

2,266 Updated today
jeremylongshore
AI & Automation Solid

vastai-deploy-integration

Deploy ML training jobs and inference services on Vast.ai GPU cloud. Use when deploying GPU workloads, configuring Docker images, or setting up automated deployment scripts. Trigger with phrases like "deploy vastai", "vastai deployment", "vastai docker", "vastai production deploy".

2,266 Updated today
jeremylongshore
AI & Automation Solid

coreweave-migration-deep-dive

Migrate ML workloads from AWS/GCP/Azure to CoreWeave GPU cloud. Use when moving inference services from hyperscaler GPU instances, migrating training pipelines, or evaluating CoreWeave vs cloud GPU costs. Trigger with phrases like "migrate to coreweave", "coreweave migration", "move from aws to coreweave", "coreweave vs aws gpu".

2,266 Updated today
jeremylongshore