Skip to content
This repository has been archived by the owner on May 3, 2022. It is now read-only.

Node Performance: Audit long closures #814

Open
kriskowal opened this issue Jun 30, 2015 · 2 comments
Open

Node Performance: Audit long closures #814

kriskowal opened this issue Jun 30, 2015 · 2 comments
Labels

Comments

@kriskowal
Copy link
Contributor

All closures should be short thunks for methods, such that those methods get tread often enough to be optimized by V8.

via #800

@Raynos
Copy link
Contributor

Raynos commented Jul 1, 2015

We should also avoid closures where possible.

@jcorbin
Copy link
Contributor

jcorbin commented Jul 1, 2015

Also another aspect is simply depth of closure nesting, preferably there should be none, but this isn't always possible... a hard limit should be around 2 or 3 in an extreme case.

@Raynos Raynos added the node label Jul 11, 2015
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

3 participants