Closed PokemonAshLovesMyTurkeyAndILikeYouTwo closed 8 years ago
Of course deflate is going be slower, it's an extra operation per message that you send. It's a gzip operation so it will be CPU heavy depending on the amount messages that you send.
@3rd-Eden Stop censoring the benchmarks to continue to defend your code. perMessageDeflate is enabled by default, which causes massive performance degradation.
ws
: The fastest RFC-6455 WebSocket implementation for Node.js.
This is simply untrue, you are lying and trying to censor / hide other modules that far surpass this module in performance.
Specifically: https://github.com/alexhultman/uWebSockets/issues/152#issue-160389186
Almost a 7-8x performance degradation even with perMessageDeflate
set to FALSE.
Streisand Effect will be in full force.
I'm not censoring benchmarks, i'm saying that deflate is of course going to be slower that one without it because of the added CPU overhead if that is not the case, then it's bug.. And you don't have to be dick and start calling people out. This is open source and free software. Don't like? Don't use it.
I closed this topic, if you're ready to have normal and civil conversation about this, feel free to create a new topic.
Top log:
perMessageDeflate: true
, second log:perMessageDeflate:false
It's mountains of times faster, why is that?
Code:
Is this a perMessageDeflate issue or my code?