You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
The text was updated successfully, but these errors were encountered: