π Option A: GitHub Repository Link
Enter any public or private GitHub repository URL to scan its files, README.md, and kernels
π Option B: Upload Files (PDF, YAML, Text, Code) or Entire Folder
Upload single files or an entire local folder to analyze alongside or instead of a GitHub link
π π
Drag & Drop Files or Folder Here
Supports
.pdf, .md, .txt, .yaml, .json, .py, .cc, .cpp, .cu, CMakeLists.txt
ποΈ Input Queue (0 local files staged)
Click any staged file below to inspect or edit its content before running analysis
| File Path | Type | Size |
|---|
Ready: Enter a GitHub URL (e.g.
https://github.com/LLNL/RAJAPerf) or upload files, then click the button below.
Detected Project / Workload
β
β
Detected Languages & Frameworks
β
β
Numeric Precision
β
Hardware Execution Format
Communication / Parallelism
β
Multi-Chip ICI Pattern
π Use-Case Summary (From Code, README.md & Uploaded Files)
Synthesized from repository tree and documentation
π Key README.md, PDF & Repository Highlights:
π¬ Inline Metrics Extracted From Files:
π§ Recommended Path to TPU & Framework Comparison
Click any framework row below to view its runnable code on the right
| Framework Path | Best Use Case | Expected Efficiency | Code |
|---|---|---|---|
1. JAX / OpenXLA (shard_map) |
SPMD Distributed Compute & Collectives | 62β67% Util | |
2. Torch-TPU (torch_xla) |
PyTorch SPMD Migration | 54β60% Util | |
3. JAX Pallas (pltpu.VMEM) |
Explicit VMEM SRAM Stencil / Attention Kernels | 68β78% Kernel Eff. | |
4. Native TPU-C (tpucc C++20) |
C++ HPC / VREG (`v1024f32`) / SparseCore / PGAS | 85%+ VPU/SC Peak | |
| 5. vLLM-TPU / MaxText | High-Throughput LLM Serving & Batching | Paged KV-Cache |
π Detailed Metrics for Selected Path
Active: JAX
ποΈ Optional: Adjust Batch / Problem Size & TPU Slice Chips (What-If Simulator)
π» Equivalent Runnable TPU Code Widget
Complete runnable implementation tailored to your analyzed workload
JAX / OpenXLA
tpu_workload_jax.py
Ready to stage to GCS & execute on GKE or Cloud TPU VMs
π 1. GCP Project Login & GCS Bucket Selection
Connect to your GCP project and select the GCS bucket for staging code & traces
β‘ 2. Select Execution Target & Run Code
Choose between your GKE Cluster TPU Node Pool or Cloud TPU VMs
π‘ Execution Console & Telemetry Logs
Staged GCS URI: Ready
Click "Stage Code to Selected GCS Bucket & Execute Workload Now" above to stage and dispatch your TPU workload.
π Generated GKE Job YAML & Runner CLI
Ready-to-run manifest pinned to your selected bucket & cluster/VM
Load Sample Issue:
π Code & Runtime Error / XProf Log Input
Paste your code and any runtime traceback or XProf warning
π¬ Root-Cause Diagnosis & Patched Code
Engine: Antigravity Agent