We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
io.js 1.6.0 landed a perf boost for parse and stringify maybe worth taking a look at? nodejs/node#847
The text was updated successfully, but these errors were encountered:
the encode method for stringifying had a substantial impact, nothing else really applies to our code base. still, was worth looking, thanks!
Sorry, something went wrong.
So did you change anything? Else this issue can be closed.
On Fri, 22 May 2015 21:03 Nathan LaFreniere notifications@github.com wrote:
the encode method for stringifying had a substantial impact, nothing else really applies to our code base. still, was worth looking, thanks! — Reply to this email directly or view it on GitHub #77 (comment).
— Reply to this email directly or view it on GitHub #77 (comment).
I did, I incorporated the encode method. Working on writing some additional tests.
OK cool, glad I could help, certainly for something that is used a lot even a small perf gain can do a lot in the long run
On Fri, 22 May 2015 21:08 Nathan LaFreniere notifications@github.com wrote:
I did, I incorporated the encode method. Working on writing some additional tests. — Reply to this email directly or view it on GitHub #77 (comment).
0c6f2a6
nlf
No branches or pull requests
io.js 1.6.0 landed a perf boost for parse and stringify maybe worth taking a look at? nodejs/node#847
The text was updated successfully, but these errors were encountered: