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

Jump to bottom

Add performance numbers for snapshot startup #15728

Closed
sethladd opened this issue Dec 19, 2013 · 2 comments
Closed

Add performance numbers for snapshot startup #15728

sethladd opened this issue Dec 19, 2013 · 2 comments
Labels
area-vm Use area-vm for VM related issues, including code coverage, FFI, and the AOT and JIT backends. closed-obsolete Closed as the reported issue is no longer relevant type-task

Comments

@sethladd
Copy link
Contributor

We have benchmarks here: http://www.dartlang.org/performance

One of the benefits of the Dart VM is faster startup with snapshots. It would be nice to have some numbers to point to for demonstrating the real performance improvements.

It was suggested that we could compile dart2js with dart2js and load/run the resulting
output with V8 to get some comparable numbers with the minified Dart source code.
@ricowind
Copy link
Contributor

ricowind commented Jan 8, 2014

+iposva
There is a number of issues with this I think:
  The compiled output of dart2js could have completely different characteristics compared to a hand written compiler in js, and the comparison would probably not be fair.
  We can't run that directly on d8 since we can't use dart:io there. Peter has a web version used for try.dartlang though, that we could use and then run it in browser, but again this is not directly comparable.

Ivan: Do you have some other existing benchmarks that we could share about this?

cc @iposva-google.
Removed Area-Infrastructure label.
Added Area-VM label.

@sethladd sethladd added type-task Priority-Unassigned area-vm Use area-vm for VM related issues, including code coverage, FFI, and the AOT and JIT backends. labels Jan 8, 2014
@mraleph
Copy link
Member

mraleph commented Apr 25, 2018

This is stale.

@mraleph mraleph closed this as completed Apr 25, 2018
@mraleph mraleph added the closed-obsolete Closed as the reported issue is no longer relevant label Apr 25, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area-vm Use area-vm for VM related issues, including code coverage, FFI, and the AOT and JIT backends. closed-obsolete Closed as the reported issue is no longer relevant type-task
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@sethladd @kevmoo @mraleph @ricowind