You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've searched for any related issues and avoided creating a duplicate issue.
Description
I know benchmarks can be highly dependent on a number of variables, but I also recall seeing stats for how many connections ws could sustain (e.g., wsbench results), would it be possible to have these metrics available?
ws version
No response
Node.js Version
No response
System
No response
Expected result
No response
Actual result
No response
Attachments
No response
The text was updated successfully, but these errors were encountered:
The answer is to run your own benchmarks. As a rule of thumb, the overhead over a plain net.Socket in terms of performance is around 10%. I'm not sure about memory usage, I have not run a benchmark for this in a long time.
Is there an existing issue for this?
Description
I know benchmarks can be highly dependent on a number of variables, but I also recall seeing stats for how many connections ws could sustain (e.g., wsbench results), would it be possible to have these metrics available?
ws version
No response
Node.js Version
No response
System
No response
Expected result
No response
Actual result
No response
Attachments
No response
The text was updated successfully, but these errors were encountered: