Output
Typed-array copy throughput
UserBenchmark / All Tools / RAM Bandwidth Test
Performance
RAM Bandwidth Test
Estimate typed-array copy throughput within JavaScript.
Free to useNo downloadNo sign-up
RAM Bandwidth Test · At a glance
Quick answer: Estimate typed-array copy throughput within JavaScript. Copied bytes divided by elapsed time produces a browser throughput estimate.
RAM Bandwidth Test
The test loads when you open it. Device access is requested only after you choose to start.
Detailed guide
How to use this tool
- Run the short typed-array copy task and repeat after closing unnecessary tabs.
- Compare only the same browser version and workload.
Input
32 MiB working set; 16 copy rounds
Browser requirement
JavaScript typed arrays; performance timing
Processing
Runs on your device; no tool-result upload
How it works and what the result means
Throughput is copied bytes divided by elapsed time. Typed-array copies involve browser and cache behavior; the result is not the same as a native DRAM bus measurement.
Reading the result
Copied bytes divided by elapsed time produces a browser throughput estimate. CPU cache, allocation and JavaScript implementation influence the value.
What to check next
Avoid comparing this directly with a native memory benchmark. A deliberately small working set prevents the page from exhausting RAM.
The working set is deliberately bounded to avoid exhausting memory. Close heavy background tabs before comparing runs.
Frequently asked questions
Why is this different from my memory data rate?
MT/s describes the memory interface, while this result measures an application copy path. They are different quantities and use different units.
How do I start the RAM Bandwidth Test?
Start the short copy benchmark and wait for the measured rounds to finish. Repeat under the same browser conditions.
Does this tool require a download or an account?
No. Open the interactive tool above in a modern browser. The instructions and explanations are available even with JavaScript disabled; running a test needs JavaScript.
Why can two attempts give different results?
Power settings, background tasks, browser scheduling, operating-system input processing and device settings affect measurements. Compare repeated attempts with identical settings rather than the single highest score.