You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[Feature Proposal]: Transition MaxText Checkpoint Conversion to Autoscaling CPU Node Pool (n2-highmem-64) #4888
Currently, MaxText checkpoint conversion (to_maxtext.py) and forward-pass logit parity verification tests are often dispatched to TPU slices (e.g., v5e / v5p).
Checkpoint conversion (weight reshaping, tensor transpositions, format transformation) is fundamentally CPU and I/O-bound rather than accelerator-compute-bound. Running these tests on TPU VMs creates several bottlenecks:
Ties up scarce TPU accelerator capacity that should be reserved for distributed model training and hardware benchmarking.
Introduces long queue wait times and preemption in Kueue/XPK.
High compute cost for workloads that do not utilize matrix multiplication units.
Proposed Solution: Standardize on Unified Autoscaling CPU Node Pool (n2-highmem-64)
We propose standardizing all MaxText checkpoint conversion and logit verification pipelines onto an Autoscaling n2-highmem-64 CPU Node Pool:
Single Standardized VM Type:
n2-highmem-64 (64 vCPUs, 512 GB RAM per node).
Provides universal coverage for all models from 2B to 70B without special-casing or infrastructure fragmentation (including dual-model on-the-fly PyTorch + MaxText logit checks for 70B models).
Scale-to-Zero (min-nodes=0, max-nodes=10):
Spins up 1 dedicated node per model on-demand when CI jobs run.
Runs all models in parallel with zero CPU thread or memory contention.
Automatically scales back down to 0 nodes when idle (zero idle cost).
Expected Benefits
Pipeline Execution Time:Identical runtime to TPU VMs, with full concurrency across all models, instant provisioning, and zero TPU queue delays.
Infrastructure Cost Reduction: >85% compute cost reduction compared to running conversion on TPU slices.
Zero Maintenance Overhead & Future-Proof: A single, consistent node pool configuration across all MaxText conversion DAGs that automatically scales as new models and PRs are added.
Action Items
Configure autoscaling n2-highmem-64 node pool (min-nodes=0, max-nodes=10) on GKE.
Hi @RexBearIU, thanks for the proposal, and for already landing the CPU flags in #4886. I'm the MaxText onduty this week and following up on next steps:
Ownership: are you planning to drive the remaining action items (setting up the autoscaling n2-highmem-64 node pool and updating the Composer/Airflow DAGs to target the CPU nodes)? Or would you like help from the MaxText team on any of them?
Hi @darisoy , thanks for following up! I've checked off the second item. Due to bandwidth right now, I'd appreciate it if the MaxText team could drive the remaining items. Thanks!
Activity
darisoy commentedon Oct 5, 2026
Hi @RexBearIU, thanks for the proposal, and for already landing the CPU flags in #4886. I'm the MaxText onduty this week and following up on next steps:
Ownership: are you planning to drive the remaining action items (setting up the autoscaling n2-highmem-64 node pool and updating the Composer/Airflow DAGs to target the CPU nodes)? Or would you like help from the MaxText team on any of them?
Since fix(testing): add CPU execution flags and standardize E2E checkpoint conversion tests #4886 is merged, could you check off the second action item so the issue shows the current status?
If you're driving this, I'll assign the issue to you so it's tracked.
Thanks!
RexBearIU commentedon Oct 6, 2026
Hi @darisoy , thanks for following up! I've checked off the second item. Due to bandwidth right now, I'd appreciate it if the MaxText team could drive the remaining items. Thanks!