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

Mapping a lambda in the IDE is very slow #1529

Closed
kustosz opened this issue Feb 26, 2021 · 0 comments · Fixed by #1564
Closed

Mapping a lambda in the IDE is very slow #1529

kustosz opened this issue Feb 26, 2021 · 0 comments · Fixed by #1564
Assignees
Labels
p-high Should be completed in the next sprint

Comments

@kustosz
Copy link
Contributor

kustosz commented Feb 26, 2021

General Summary

There's a huge performance discrepancy between calling my_vec.map x-> x.do_something 10
in the IDE and in the CLI. The discrepancy on my data is on the order of 5 seconds in the CLI vs. 20 minutes in the IDE.
Note that this only happens with lambdas (both -> and _) but not with curried methods,
I.e. the same lambda extracted to a module level method and passed to map like here.my_fun is fast in the IDE.
Because of this effect, my assumption is that the instrumentation framework triggers for nodes inside the lambda.

Steps to Reproduce

Map a semi-involved lambda over a large vector.

Expected Result

Same speed in CLI and IDE

Actual Result

Significant slowdown in the IDE

Enso Version

New one :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
p-high Should be completed in the next sprint
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants