Skip to content
This repository was archived by the owner on Oct 24, 2023. It is now read-only.

Track performance #16

Closed
mstade opened this issue May 4, 2014 · 1 comment
Closed

Track performance #16

mstade opened this issue May 4, 2014 · 1 comment

Comments

@mstade
Copy link
Owner

mstade commented May 4, 2014

This project could benefit from a suite of performance tests. Not sure what the best approach to this is; perhaps a good start would be to proxy unit tests to introduce instrumentation of tested functions. Not sure whether this is relevant or whether it's just pointless micro-benchmarking.

Some good performance tips can be found in this screencast: https://vimeo.com/68085383

Particularly the notes on binding, call/apply, and inspecting functions looking for this to see whether binding is necessary. That last point is very relevant for #11.

@mstade
Copy link
Owner Author

mstade commented Jan 31, 2015

Have no idea how to track this, might revisit some other time.

@mstade mstade closed this as completed Jan 31, 2015
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant