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.

Sign up for GitHub

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

Compilation of promise resolution and message sending not optimal #247

Open
smarr opened this issue Apr 26, 2018 · 0 comments
Open

Compilation of promise resolution and message sending not optimal #247

smarr opened this issue Apr 26, 2018 · 0 comments
Labels
enhancement Improves the implementation with something noteworthy help wanted Would be great if you could help out here.

Comments

@smarr
Copy link
Owner

smarr commented Apr 26, 2018

Currently, PromiseMessage.resolve() and EventualMessage.getTarget() cannot be inlined, because they are not devirtualized.
Might give a bit of performance improvement to fix these.
Probably not a lot, but might be worth doing.

The screenshot below is from a run of:

./debug -i -t1 -at -TF -sid -EG core-lib/Benchmarks/AsyncHarness.ns Savina.ForkJoinActorCreation 1000 0 40000

screen shot 2018-04-26 at 18 00 18
@smarr smarr added enhancement Improves the implementation with something noteworthy help wanted Would be great if you could help out here. labels Apr 26, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement Improves the implementation with something noteworthy help wanted Would be great if you could help out here.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@smarr