Skip to content

Benchmark improvements #176

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

Merged
merged 1 commit into from
Apr 3, 2022
Merged

Benchmark improvements #176

merged 1 commit into from
Apr 3, 2022

Conversation

jamesdbrock
Copy link
Member

Added and removed some benchmarks.
Benchmark section headers.

@jamesdbrock jamesdbrock force-pushed the benchrec branch 2 times, most recently from 74718ec to 2ae293f Compare April 3, 2022 04:18
@jamesdbrock
Copy link
Member Author

jamesdbrock commented Apr 3, 2022

(comment lost due to a mistake)

Added and removed some benchmarks.
Benchmark section headers.
$ \_ -> runParser string23_1000 $ sepByRec anyChar (char '3')

log "<th><h2>sepBy 10000</h2></th>"
-- sepBy not stack-safe
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

A stack unsafe parser should be a bug, right?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes I think so?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm going to merge these benchmarks, then let's talk about it.

@jamesdbrock jamesdbrock merged commit c695f6a into main Apr 3, 2022
@jamesdbrock jamesdbrock deleted the benchrec branch April 3, 2022 04:24
@natefaubion
Copy link
Contributor

It's not clear to me that runTrampoline is useful other than to prove that it has no effect. runTrampoline on a pure parser is a noop.

@jamesdbrock
Copy link
Member Author

It's not clear to me that runTrampoline is useful other than to prove that it has no effect. runTrampoline on a pure parser is a noop.

Yeah, maybe having proven that runTrampoline is a no-op, we could remove that benchmark.

@jamesdbrock jamesdbrock mentioned this pull request Apr 3, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

2 participants