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

Investigate some cases for performance #141

Open
harendra-kumar opened this issue Nov 22, 2018 · 1 comment
Open

Investigate some cases for performance #141

harendra-kumar opened this issue Nov 22, 2018 · 1 comment
Labels
type:performance impacts performance

Comments

@harendra-kumar
Copy link
Member

  1. aheadly applicative tests (maxBuffer?) in Prop.hs seem to run quite slowly
  2. maxBuffer 1 test for aheadly seems to run very slow

We need to check if there is an opportunity for optimization in these cases.

@harendra-kumar harendra-kumar added the type:performance impacts performance label Nov 22, 2018
@harendra-kumar
Copy link
Member Author

Some other performance related investigations:

  1. The benchmark routine "benchIO" in streaming-benchmarks as well as in streamly benchmarks needs to be INLINEd for streamly and conduit but not for vector. Why?
  2. parallely/zip benchmark has degraded from 32ms to almost 50 ms over time. need to see if this can be improved again.
  3. When mapM is used with unfoldrM and both are used aheadly, the results are much
    worse compared to asyncly.
  4. filterSome with aheadly seems to perform pretty badly when using a 1000x1000 iterations.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type:performance impacts performance
Projects
None yet
Development

No branches or pull requests

2 participants