Skip to content

Improve performance by avoiding unneeded promise wrapping #292

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

Merged
merged 1 commit into from
Dec 30, 2017

Conversation

clue
Copy link
Member

@clue clue commented Dec 30, 2017

This very simple PR avoids wrapping the return value from the request handler in another promise. The request handler will either return a promise or a value that can be consumed directly. When running example 99 with included benchmarking instructions, this simple change improves performance from ~2400 req/s to ~2500 req/s on my local machine.

Builds on top of #291

@clue clue added this to the v0.8.1 milestone Dec 30, 2017
jsor
jsor previously approved these changes Dec 30, 2017
}

// did not return a promise? this is an error, convert into one for rejection below.
if (!$response instanceof PromiseInterface) {
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This if should probably omitted and promise conversion should be completely delegated to resolve().

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm not opposed to your suggestion, but after trying this out locally, the performance improvement is much less significant. Do you feel this is more of a cosmetic issue or would this block these suggested changes?

@jsor jsor dismissed their stale review December 30, 2017 16:10

Accidentally approved ;)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants
pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy