gpu.rocks valid
GPU.js
GPGPU in pure JavaScript: gpu.js compiles JavaScript functions into shader
Their llms.txt
The beginning of the file, from our validated copy saved 2026-10-26T08:04:23.681Z. Cached copy · Source on gpu.rocks
# GPU.js
> GPGPU in pure JavaScript: gpu.js compiles JavaScript functions into shader
> code and runs them on the GPU, falling back to the CPU when there is no
> GPU available. gpu.rocks also hosts a free, hands-on GPGPU course that runs
> entirely in the browser.
Every page below is also available as Markdown by appending `.md` to its URL.
The whole course in one file: https://gpu.rocks/llms-full.txt
## Site
- [GPU.js — GPU accelerated JavaScript](https://gpu.rocks/index.md): GPGPU operations using pure JavaScript. gpu.js compiles your JavaScript functions into shader code and runs them on your GPU — with a CPU fallback.
- [Benchmark — GPU.js](https://gpu.rocks/benchmark.md): Thirty GPGPU workloads timed in your browser on every backend gpu.js can reach — WebGPU, WebGL2, WebGL, WebAssembly and CPU — against hand-written implementations with no gpu.js in them. Every answer is checked against a plain-JavaScript oracle before it is timed.
- [Installation — GPU.js](https://gpu.rocks/install.md): Install GPU.js from npm, yarn, or a CDN script tag and write your first GPU-accelerated JavaScript kernel in the browser or Node.js.
- [Examples — GPU.js](https://gpu.rocks/examples.md): GPU.js examples: matrix multiplication and more GPGPU snippets you can read, run, and benchmark on your own graphics card.
- [Learn GPGPU in your browser — GPU.js Learn](https://gpu.rocks/learn.md): A free hands-on GPGPU course built on gpu.js: write real kernels in your browser, run them on your own GPU, and learn ideas that transfer to CUDA and WebGPU.
## Course — GPGPU 101
From zero to your first thousand threads
- [Hello, Kernel](https://gpu.rocks/learn/hello-kernel-f1399353.md): What a kernel is, what a thread is, and why this.thread.x replaces your for-loop.
- [Data In, Data Out](https://gpu.rocks/learn/data-in-data-out-42b68d01.md): Feeding arrays and images into kernels, shaping 1D/2D/3D output, and reading results back.
- [Pipelines & Textures](https://gpu.rocks/learn/pipelines-and-textures-9f4aeaa5.md): Chaining kernels so data stays on the GPU — the single biggest real-world speedup.
- [Measuring Speed Honestly](https://gpu.rocks/learn/measuring-speed-honestly-b9188894.md): Warm-up, transfer costs, and precision — when the GPU wins, and when the CPU quietly beats it.
## Course — Parallel Primitives
The handful of patterns everything else is built from
- [Thinking in Parallel](https://gpu.rocks/learn/thinking-in-parallel-c3876efb.md): Map and gather patterns, why kernels write only their own cell, and how to design around it.
- [Reductions](https://gpu.rocks/learn/reductions-3dadc130.md): Sum, min, max and mean over millions of values — the ladder pattern every platform uses.
- [Prefix Sums (Scan)](https://gpu.rocks/learn/prefix-sum-351cfa41.md): Running totals in parallel — the doubling ladder, exclusive scans, and the offsets every variable-sized output depends on.
- [Stream Compaction](https://gpu.rocks/learn/stream-compaction-0aed2e43.md): Filtering o
…
Related sites
Similar publisher descriptions and documentation. Similarity does not imply affiliation or equivalent capabilities.
| Domain | Title | Category | Country | Authority | llms.txt | llms-full.txt | Save |
|---|---|---|---|---|---|---|---|
| irendering.net | iRender - Next-Gen GPU Cloud Computing Platform, GPU Render Farm | transactional Infrastructure | SG | 47 | ✓ | ||
| threejs.org | Three.js | documentation Developer tools Open source projects | US | 54 | ✓ | ||
| pixijs.com | PixiJS Documentation for LLMs | documentation Developer tools Documentation and reference +1 | US | 63 | ✓ | ✓ | |
| w.ai | w.ai Documentation | documentation Infrastructure AI and machine learning | — | 56 | ✓ | ✓ | |
| gpu.net | GPUNET Enterprise | transactional Infrastructure AI and machine learning | — | 45 | ✓ | ✓ | |
| flaviocopes.com | Flavio Copes | documentation Developer tools Open source projects +1 | — | 58 | ✓ | ✓ | |
| numpyts.dev | numpy-ts | documentation Developer tools | — | 46 | ✓ | ✓ | |
| vessl.ai | VESSL AI | documentation AI and machine learning Developer tools +1 | — | 50 | ✓ | ✓ |
Machine-readable: GET /v1/resolve?q=gpu.rocks · GET /v1/domain/gpu.rocks · this page as Accept: application/json or text/markdown · MCP lookup_domain
Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.
Own or manage this website?
If you own or manage gpu.rocks, you can update its listing and review file health, discovery activity and score history.
Manage this listing — optional
What verification unlocks
See how your site is discovered—and control what agents see.
- See your website in the map
Review your indexed topics, nearby publishers sharing headings, measured listing exposure and map snapshots in a private report for your website.
- Control what agents see
Edit your listing description, tags, public contact details and additional llms.txt paths. Publish your terms for automated access, attribution and pricing.
- Make your profile eligible for search
A valid, listed, unblocked, verified profile can appear in our publisher sitemap and become eligible for search-engine visibility. Search engines decide what to index and rank.
- Appear in our llms-full.txt
Eligible verified publishers are listed by name, with their file links and summaries, in the service overview agents can read.
Free. No account registration, backlink or payment required. Public discovery remains available without verification.
Let your coding agent verify it
If your coding agent is authorized to manage this website, paste these instructions into it.
Claim my listing on Agent Web Map for gpu.rocks:
1. POST https://agentwebmap.com/v1/sites/gpu.rocks/claims and keep claim_id and claim_secret private.
2. Publish the verification line "AgentWebMap verification: <token>" (token from step 1) in https://gpu.rocks/llms.txt, or use the DNS, meta-tag or well-known method the response describes. This only verifies the listing; your website and domain remain yours.
3. POST https://agentwebmap.com/v1/sites/gpu.rocks/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/gpu.rocks).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verifyCorrections or removal requests: contact the directory.