3 ms·
I always use the following replacements written by petkaanotonov, the author of bluebird :) https://www.npmjs.com/package/querystringparser https://www.npmjs.c
by spion 12y ago
I always use the following replacements written by petkaanotonov, the author of bluebird :)
https://www.npmjs.com/package/querystringparser https://www.npmjs.com/package/querystringparser for query string parsing. Depending on content, you may get massive improvements (5x-20x)
https://www.npmjs.com/package/fast-url-parser https://www.npmjs.com/package/fast-url-parser for url parsing (the built in url parser is the main reason why node is so far behind on the TechEmpower benchmark - with this replacement the benchmark shows about 60-80% improvement in served req/s)
https://www.npmjs.com/package/cookieparser https://www.npmjs.com/package/cookieparser
For very large post bodies, I use JSON in conjunction with OboeJS - http://oboejs.com/ http://oboejs.com/ . Its not too much slower than native JSON.parse (about 5-7 times) however its non-blocking. Still haven't found a solution that is close enough in speed to native JSON.parse
- cddotdotslash 12y agoThese look promising, thanks!
- kapv89 12y agoThis comment in itself is probably more valuable than the OP