search

GraftJS / jschan

JavaScript port of libchan based around streams
MIT License
157 stars 9 forks source link

Performance Analysis #17

Open mcollina opened 9 years ago

mcollina commented 9 years ago

How this is slower than standard streams? How this is slower than HTTP?

We just need some numbers, and maybe some optimization tricks.

AdrianRossouw commented 9 years ago

This issue is a bit 'how long is a piece of string'. Can we maybe think of some more concrete things that could be tested for?

At least for standard streams, we could likely prove how much slower it is than a local operation over the memory transport. It runs mempack etc on the data the whole time too, right?

As for HTTP, it's quite different in nature. But I guess 'fetching an json document', 'uploading a png'.

We might want to collaborate with the libchan guys though, because a benchmarking suite could theoretically be used for all implementations, right?

mcollina commented 9 years ago

Yes, indeed. This might need some thinking, but having some preliminary benchmark maybe useful. We need to know how this stacks up against Express, ecc. Especially in the websocket scenario!

heri16 commented 9 years ago

Agreed.

mcollina commented 9 years ago

would you like to give it a spin? Send a PR with your bench scripts! :) Il giorno gio 8 gen 2015 alle 12:30 heri16 notifications@github.com ha scritto:

Agreed.

— Reply to this email directly or view it on GitHub https://github.com/GraftJS/jschan/issues/17#issuecomment-69167776.