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 results don't mention multipart-parser #8

Open
ronkorving opened this issue Jul 8, 2015 · 3 comments
Open

Benchmark results don't mention multipart-parser #8

ronkorving opened this issue Jul 8, 2015 · 3 comments

Comments

@ronkorving
Copy link

It might be nice to add a comparison to multipart-parser, which is a lot older but also claims insane speeds.

@mscdex
Copy link
Owner

mscdex commented Jul 8, 2015

IIRC that's more or less what is used in formidable/multiparty, just parted out into its own module.

@ronkorving
Copy link
Author

I wasn't aware of that, thanks for explaining. Perhaps the benchmark page does deserve an update though? It's 2015 :)

@mscdex
Copy link
Owner

mscdex commented Jul 9, 2015

I suppose so, but AFAIK the underlying algorithms haven't really changed in dicer, multiparty, or formidable. I'm not sure about the other modules.

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