mirror of
https://github.com/denoland/deno.git
synced 2024-11-21 15:04:11 -05:00
e92a05b551
Adds a `parallel` flag to `deno serve`. When present, we spawn multiple workers to parallelize serving requests. ```bash deno serve --parallel main.ts ``` Currently on linux we use `SO_REUSEPORT` and rely on the fact that the kernel will distribute connections in a round-robin manner. On mac and windows, we sort of emulate this by cloning the underlying file descriptor and passing a handle to each worker. The connections will not be guaranteed to be fairly distributed (and in practice almost certainly won't be), but the distribution is still spread enough to provide a significant performance increase. --- (Run on an Macbook Pro with an M3 Max, serving `deno.com` baseline:: ``` ❯ wrk -d 30s -c 125 --latency http://127.0.0.1:8000 Running 30s test @ http://127.0.0.1:8000 2 threads and 125 connections Thread Stats Avg Stdev Max +/- Stdev Latency 239.78ms 13.56ms 330.54ms 79.12% Req/Sec 258.58 35.56 360.00 70.64% Latency Distribution 50% 236.72ms 75% 248.46ms 90% 256.84ms 99% 268.23ms 15458 requests in 30.02s, 2.47GB read Requests/sec: 514.89 Transfer/sec: 84.33MB ``` this PR (`with --parallel` flag) ``` ❯ wrk -d 30s -c 125 --latency http://127.0.0.1:8000 Running 30s test @ http://127.0.0.1:8000 2 threads and 125 connections Thread Stats Avg Stdev Max +/- Stdev Latency 117.40ms 142.84ms 590.45ms 79.07% Req/Sec 1.33k 175.19 1.77k 69.00% Latency Distribution 50% 22.34ms 75% 223.67ms 90% 357.32ms 99% 460.50ms 79636 requests in 30.07s, 12.74GB read Requests/sec: 2647.96 Transfer/sec: 433.71MB ``` |
||
---|---|---|
.. | ||
01_errors.js | ||
01_version.ts | ||
06_util.js | ||
10_permissions.js | ||
11_workers.js | ||
13_buffer.js | ||
30_os.js | ||
40_fs_events.js | ||
40_process.js | ||
40_signals.js | ||
40_tty.js | ||
41_prompt.js | ||
90_deno_ns.js | ||
98_global_scope_shared.js | ||
98_global_scope_window.js | ||
98_global_scope_worker.js | ||
99_main.js | ||
README.md |
Runtime JavaScript Code
This directory contains Deno runtime code written in plain JavaScript.
Each file is an ES module and is prefixed with a number, telling in which order scripts should be loaded into V8 isolate.
Deno Web APIs
This directory facilities Web APIs that are available in Deno.
Please note, that some implementations might not be completely aligned with specification.
Some Web APIs are using ops under the hood, eg. console
, performance
.
Implemented Web APIs
- Blob: for representing opaque binary data.
- Console: for logging purposes.
- CustomEvent,
EventTarget
and
EventListener:
to work with DOM events.
- Implementation notes: There is no DOM hierarchy in Deno, so there is no tree for Events to bubble/capture through.
- fetch, Request, Response, Body and Headers: modern Promise-based HTTP Request API.
- location and Location.
- FormData: access
to a
multipart/form-data
serialization. - Performance: retrieving current time with a high precision.
- setTimeout, setInterval, clearTimeout: scheduling callbacks in future and clearInterval.
- Stream for creating, composing, and consuming streams of data.
- URL and URLSearchParams: to construct and parse URLSs.
- Worker: executing
additional code in a separate thread.
- Implementation notes: Blob URLs are not supported, object ownership cannot be transferred, posted data is serialized to JSON instead of structured cloning.