-
-
Notifications
You must be signed in to change notification settings - Fork 17
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bugfix/48 #49
Bugfix/48 #49
Conversation
fix: replaced Object.assign with spread
fix: replaced Object.assign with spread
commit: |
package.json
Outdated
@@ -59,7 +59,7 @@ | |||
"statuses": "^2.0.1", | |||
"tseep": "^1.2.2", | |||
"type-is": "^1.6.18", | |||
"uWebSockets.js": "github:uNetworking/uWebSockets.js#v20.49.0", | |||
"uWebSockets.js": "github:uNetworking/uWebSockets.js#v20.70.0", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There's no 20.70.0 uWS.js, you're confusing it with C++ uWS
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
you are right. I was looking at the C++ version.
add: benchmark for object creation add: benchmark workflow
@dimdenGD I am finished with this now if you want to review. |
Why do {...new NullObject()}? It's like creating a fast object and then creating a slow one and putting it inside. Would be faster to just have {} at this point |
My initial thoughts. But ran some benchmarks, and seems it's faster like this. See if you get the same results from it? |
I don't see how it's possible for it to be faster that way. Microbenchmarks are often deceptive |
You should probably test some reads+writes too. Also there's no point in using these spreads for internal stuff only used by library, only for public things like req.query and req.params |
closes #48