About
As part of Deno's continuous integration and testing pipeline we measure the performance of certain key metrics of the runtime. You can view these benchmarks here.
You are currently viewing data for the most recent commits to the main branch. You can also view all commits or append e.g. ?-100 to this page's URL to view results for the last 100 commits.
Runtime Metrics
In this section we measure various metrics of the following scripts:
- cold_relative_import
- text_decoder
- error_001
- cold_hello
- workers_round_robin
- relative_import
- workers_startup
- hello
Execution time
This shows how much time total it takes to run a script. For deno to execute typescript, it must first compile it to JS. A warm startup is when deno has a cached JS output already, so it should be fast because it bypasses the TS compiler. A cold startup is when deno must compile from scratch.
Execution time (Web Workers)
This shows how much time total it takes to run a script. For deno to execute typescript, it must first compile it to JS. A warm startup is when deno has a cached JS output already, so it should be fast because it bypasses the TS compiler. A cold startup is when deno must compile from scratch.
Thread count
How many threads various programs use. Smaller is better.
Thread count (Web Workers)
How many threads various programs use. Smaller is better.
Syscall count
How many total syscalls are performed when executing a given script. Smaller is better.
Syscall count (Web Worker)
How many total syscalls are performed when executing a given script. Smaller is better.
Max memory usage
Max memory usage during execution. Smaller is better.
Max memory usage (Web Worker)
Max memory usage during execution. Smaller is better.
Size
File sizes
We track the size of various files here. "deno" is the release binary.
Cargo Dependencies
Language Server
We track the performance of the Deno language server under different scenarios to help gauge the overall performance of the language server.