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

What do the x and y axises mean on the performance graphs? #1

Closed
grepsedawk opened this issue Apr 1, 2018 · 2 comments
Closed

What do the x and y axises mean on the performance graphs? #1

grepsedawk opened this issue Apr 1, 2018 · 2 comments

Comments

@grepsedawk
Copy link

The performance is shown as faster, but what are the x and y axises? Are they the total count mapped over and a unit of time?

@zwilias
Copy link
Owner

zwilias commented Apr 1, 2018

ilias [10:15 PM]
Horizontal is the size of the list, vertical is the number of list-items processed per second.
For very small lists, things like the overhead of calling a function dominate. When you go a little further along, things tend to settle a bit. Eventually, garbage collection needs to kick in every now and then because foldr and map tend to create intermediate structures and as the sizes grow, so does the generated garbage.

Note that both axes are logarithmic. This makes the plots a little harder to interpret, but it looked prettied. So for example for List.foldr with a List with 10.000 entries, this means that the "next implementation in elm-lang/core" (next, the yellow line) is able to process ~3.000 elements per second, while the implementation in this repo manages ~30.000 elements per second.

@grepsedawk
Copy link
Author

grepsedawk commented Apr 1, 2018 via email

@zwilias zwilias closed this as completed Apr 2, 2018
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

No branches or pull requests

2 participants