tsctx
tsctx
Hi @AriPerkkio, Is this fixed in the latest node (v21.7.1)? A Webstream fix patch (nodejs/node#51526) has been added. It seems to have fixed this issue.
Fixed by #3375
@ronag Benchmarks updated and performance improved. Can you take a look at it?
```shell > $ node ./benchmarks/websocket-benchmark.mjs (node:9028) [UNDICI-WSS] Warning: WebSocketStream is experimental! Expect it to change at any time. (Use `node --trace-warnings ...` to show where the warning was created) undici...
@lpinca There was a difference in performance due to the number of iterations, and increasing the number to 512 would have produced more correct results. ```shell > $ node ./benchmarks/websocket-benchmark.mjs...
What do you think of this? https://github.com/tsctx/ws-masking/blob/main/initialize.js It uses int32 and processes 4 chunks at a time, making it 8 times faster than the current implementation.
> Is there a reason to combine method validation and normalization into a single method? The reason for wanting to normalize and verify at the same time is that the...
> Can you share the bench results? ```js import Request from "../../lib/core/request.js"; import DecoratorHandler from "../../lib/handler/decorator-handler.js"; import { bench, group, run } from 'mitata' const handler = new DecoratorHandler({}) bench('new...
If not properly shuffled to balance the left and right sides, it will cause a bad case and further degrade performance. This is similar to the problem with binary trees.