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

Dartium WebSocket performance #16219

Closed
iposva-google opened this issue Jan 20, 2014 · 1 comment
Closed

Dartium WebSocket performance #16219

iposva-google opened this issue Jan 20, 2014 · 1 comment
Labels
closed-obsolete Closed as the reported issue is no longer relevant

Comments

@iposva-google
Copy link
Contributor

Forked from https://code.google.com/p/dart/issues/detail?id=15134#c8

I downloaded the latest devchannel release (1.1.0-dev.5.11) to see how it changed.
The performance differences between setAll and setRange are gone.
For the Dart VM I could only see a minor performance improvement. I can now transfer 270MB/s using a plain TCP/IP connection on localhost and 100MB/s using a Dart IO websocket connection.

For Dart2Js the difference is very obvious. I can now send using WebSockets on Firefox with 200MB/s, which is quite amazing for a websocket connection. Dartium is unfortunatly quite behind at 60MB/s. Current Chrome release is a little bit higher with 80MB/s.

So all in all from the array handling point of view it seems OK now. The critical pathes now seem to be the IO and especially the websocket implementations.

@vsmenon
Copy link
Member

vsmenon commented Jul 16, 2014

It looks like we were 25% slower (80 vs 60) than V8/ Chrome back in Jan. Perhaps we've caught up since.


cc @a-siva.
Set owner to @leafpetersen.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
closed-obsolete Closed as the reported issue is no longer relevant
Projects
None yet
Development

No branches or pull requests

4 participants