Repository navigation
Conversation
Contributor
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Automations to automatically generate PRs for you. |
yummybomb
force-pushed
the
hypeship/large-gpu-browsers
branch
from
October 6, 2026 19:35
f59cce7 to
9843b1b
Compare
yummybomb
force-pushed
the
hypeship/large-gpu-browsers
branch
from
October 6, 2026 20:02
9843b1b to
2aec501
Compare
yummybomb
force-pushed
the
hypeship/large-gpu-browsers
branch
from
October 6, 2026 22:00
2aec501 to
8d65f3c
Compare
yummybomb
force-pushed
the
hypeship/large-gpu-browsers
branch
from
October 7, 2026 14:02
8d65f3c to
068448b
Compare
yummybomb
force-pushed
the
hypeship/large-gpu-browsers
branch
from
October 9, 2026 21:22
068448b to
4ea2fc5
Compare
yummybomb
changed the title
This branch was successfully deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Documents
video_memory, which requests a GPU browser with 4 GiB of video memory, 8 vCPUs, and 12 GiB of memory. The API, the SDKs (0.123.0), and the CLI (0.47.0,--video-memory) all support it.browsers/gpu-acceleration.mdx: new "Request more video memory" section with TypeScript, Python, Go, and CLI examples. It covers the allowed values, the requirement thatgpuistrue, the fact thatmemorycan't be set on GPU browsers, the response fields, billing, and the 529no_gpu_browsers_availableresponse when this tier is at capacity. It doesn't fall back to a standard GPU browser.browsers/process-execution.mdx: the whole-session memory paragraph now covers GPU allocations (6 GiB, or 12 GiB with 4 GiB of video memory).info/pricing.mdx: new usage-rate row at0.0016000032 $/sec, twice the standard GPU rate. Sessions with 4 GiB of video memory report 12 GB to billing instead of 6, and the GPU rate is metered per GB.changelog.mdx: October 9 entry.Replaces the earlier draft of this PR, which documented
memory: "12GiB". The shipped API rejectsmemorywhengpuistrueand usesvideo_memoryinstead.Before merging
snippets/calculator.jsx) still has a single GPU option and isn't updated here.mint broken-linkspasses. I didn't render the pages locally.