Navigation Menu

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

track native function call performance #15340

Open
DartBot opened this issue Nov 26, 2013 · 3 comments
Open

track native function call performance #15340

DartBot opened this issue Nov 26, 2013 · 3 comments
Labels
area-vm Use area-vm for VM related issues, including code coverage, FFI, and the AOT and JIT backends. type-performance Issue relates to performance or code size

Comments

@DartBot
Copy link

DartBot commented Nov 26, 2013

This issue was originally filed by rb...@radix.io

This issue is here to track function call performance of native extensions.

At the moment (r30667), calling a empty native function 1 million times takes about 15μs.
Lets improve that.
@iposva-google
Copy link
Contributor

Added Area-VM, Triaged labels.

@DartBot
Copy link
Author

DartBot commented Nov 27, 2013

This comment was originally written by rb...@radix.io

I have not checked the load on the machine I tested that on.
Here are the new numbers.
Tested on:
mac mini Core 2 T5600
Linux 3.12.1
load average: 0.45
dart r30667

gcc 4.8.2, flags = -fPIC -m64 -O2
1000000 x call native function with one String as argument. 76 in length. 49 ms (noop function)
1000000 x call dart function with one String as argument. 76 in length. 3 ms (noop function)

@DartBot
Copy link
Author

DartBot commented Jan 7, 2014

This comment was originally written by rb...@radix.io

New numbers, same machine.
With dart (r31459)

1000000 x call native function with one String argument 76 in length. 58 ms
1000000 x call dart function with one String argument 76 in length. 3 ms

@DartBot DartBot added Type-Defect area-vm Use area-vm for VM related issues, including code coverage, FFI, and the AOT and JIT backends. labels Jan 7, 2014
@kevmoo kevmoo added type-bug Incorrect behavior (everything from a crash to more subtle misbehavior) and removed priority-unassigned labels Feb 29, 2016
@zanderso zanderso added type-performance Issue relates to performance or code size and removed type-bug Incorrect behavior (everything from a crash to more subtle misbehavior) labels Jun 23, 2016
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. type-performance Issue relates to performance or code size
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@kevmoo @iposva-google @zanderso @DartBot