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

Update bench for 2020 #13

Merged
merged 3 commits into from
Mar 1, 2021
Merged

Conversation

fendor
Copy link
Contributor

@fendor fendor commented Jul 10, 2020

Not sure if something like this is wanted anymore, but I repeated the benchmarks out of curiosity and thought, maybe it is interesting.

Basic benchmark information:

Compiler: GHC 8.8.3
Run: stack bench :time && ./Report.hs out.csv
RAM: 32GB (4*8GB) DDR4 3600 MT/s
CPU: AMD Ryzen 7 3800X 8-Core Processor

@chrisdone
Copy link
Member

Thanks.

I think it's hard to tell what this is benchmarking without a stack.yaml update. An lts-resolver would tell people what GHC version and what versions of each package is being tested.

As it stands, your submitted PR shows that for some unknown package versions for an undocumented GHC, these are some results.

If you were running a stack bench :time, you would expect to see basically the same ratios with respect to eachother. If your machine was 10x faster, the numbers would be smaller, but they'd all still show the same proportions to one another like they do from my laptop. If the packages have been modified for better performance, you'd see different proportions, but as it stands we don't know what those packages are for sure.

If you want to try with stack on the current resolver and then try on a latest resolver that uses GHC 8.8.3, I'd be interested to see the difference in numbers.

@fendor
Copy link
Contributor Author

fendor commented Mar 1, 2021

Better late than never, right? Finally found the time to re-run the benchmarks with stack.

@chrisdone
Copy link
Member

Looks good!

@chrisdone chrisdone merged commit 80fb472 into haskell-perf:master Mar 1, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants