Benchmark TinyStories with Google DDP and an AI agent
Review frequently asked questions
These FAQs were drafted with an approved AI-assisted workflow and reviewed by Arm contributors before publication. Human technical review remains part of the process so the final page reflects engineering rigor, accuracy, and Arm editorial standards.
Have the Google Cloud CLI, Antigravity CLI, and Python installed. Ensure that Node.js,
curl, adb, and scrcpy are available on your development computer. Use a Google Cloud project with billing enabled and the necessary permissions. Sign in to the CLI, configure Application Default Credentials (ADC), and enable the three DDP services.Check that
gcloud shows your intended active account and project, and that ADC can obtain a token. Confirm that devicerun.googleapis.com, devicestreaming.googleapis.com, and testing.googleapis.com are enabled. Inspect the device catalog for a physical configuration with streaming support.You describe the phone and task in
agy. Antigravity checks availability, prepares the reservation, connects the phone, and opens its screen. Before a billable session starts, review the proposed project, device, Android version, duration, and estimated cost. After review, approve the reservation in agy.Check that GPU offload was disabled and that both paths used the same model, quantization, inputs, thread count, and CPU placement. Check that Antigravity confirmed output agreement before timing and used repeated, warmed-up measurements. Review prompt-processing and token-generation results separately. Review the saved report for throughput, variation, and evidence of which Arm kernels ran.
Check that Antigravity canceled the recorded DDP session and confirmed its cloud state is
FINISHED or EXPIRED. Closing the viewer alone doesn’t stop billing. If the task stops early, ask Antigravity to release the session and verify its state.