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

recent parser performance regression #15262

Closed
vtjnash opened this issue Feb 27, 2016 · 2 comments
Closed

recent parser performance regression #15262

vtjnash opened this issue Feb 27, 2016 · 2 comments
Assignees
@JeffBezanson
Labels
parser Language parsing and surface syntax performance Must go faster regression Regression in behavior compared to a previous version

Comments

@vtjnash
Copy link
Member

vtjnash commented Feb 27, 2016

With the recent work on modifying julia-syntax, I assumed it should be faster now. However, I was surprised to find that f5033ad seemed to be about twice as fast on one of my torture benchmarks (#9729 (comment)) than both v0.4 and master today (636916e).

(there's nothing special about that first commit, i just usually try to have one build on my machine that lags behind my current work)
@vtjnash vtjnash added performance Must go faster regression Regression in behavior compared to a previous version parser Language parsing and surface syntax labels Feb 27, 2016
@nalimilan
Copy link
Member

Any chance it could be related with #15246?

@JeffBezanson JeffBezanson self-assigned this Mar 12, 2016
@vtjnash vtjnash mentioned this issue Mar 21, 2016
Closed
@vtjnash
Copy link
Member Author

vtjnash commented Nov 29, 2016

Looks like this was fixed in v0.5

@vtjnash vtjnash closed this as completed Nov 29, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@JeffBezanson JeffBezanson

Labels
parser Language parsing and surface syntax performance Must go faster regression Regression in behavior compared to a previous version
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@vtjnash @JeffBezanson @nalimilan