Skip to content
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

Benchmark! #4

Open
chrisui opened this issue Apr 18, 2016 · 1 comment
Open

Benchmark! #4

chrisui opened this issue Apr 18, 2016 · 1 comment

Comments

@chrisui
Copy link
Owner

chrisui commented Apr 18, 2016

So in theory this plugin is great. We prevent the breaking of purity throughout our components transparently so should be able to avoid lots of re-renders without having to manually manage our bound functions and their references.

However, there is obviously some performance cost from doing the memoized bind so it would be good to have some very clear benchmarks which would demonstrate this and allow us to decide whether the optimisation is worth it or not.

These benchmarks should help:

  • Determine whether this is even a viable solution (though the work done here should be what we do in our components anyway to keep purity)
  • Determine location (per instance? per component?) of cache and size (dynamic? best default static?)
  • Prevent performance regressions in future releases and allow people to test different caching algorithms
@giacomorebonato
Copy link

I love this project's idea. Writing function in the render method is so easy to read.... I am not good at benchmarking, but I will study. Thanks.

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

No branches or pull requests

2 participants