Skip to content
This repository has been archived by the owner on Feb 5, 2021. It is now read-only.

Automated performance testing #88

Open
tarcieri opened this issue Oct 8, 2017 · 2 comments
Open

Automated performance testing #88

tarcieri opened this issue Oct 8, 2017 · 2 comments

Comments

@tarcieri
Copy link
Contributor

tarcieri commented Oct 8, 2017

It looks like performance regressed rather severely in a commit reverted here:

#87

It would be nice to detect such regressions automatically and prevent them in the future

@vaibhavsingh1993
Copy link

vaibhavsingh1993 commented Nov 27, 2017

Hi,
I can help out with a performance tool for the JavaScript implementation if you are not working on it already.

@tarcieri
Copy link
Contributor Author

tarcieri commented Nov 27, 2017

@vaibhavsingh1993 that'd be great! In particular I'd be curious about in-browser performance, possibly using something like PhantomJS?

On the Node side I'd like to support a native Rust backend using Neon, so I'm less concerned about the performance of the existing code on Node.

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

No branches or pull requests

2 participants