Harendra Kumar

Ah, I did not know that it has been special cased for hfsevents. I did another experiment. In the streamly package, I added a Haskell dependency under the conditional: ```...

I am observing a similar behavior. When I add a second benchmark the first one takes longer time. The two pieces of code I am benchmarking are completely unrelated. Also...

It seems my problem was due to the sharing of input data across benchmarks which caused undue memory pressure for the later benchmarks. The problem got resolved by using `env`....

@RyanGlScott I am aware of #60 but this may not be the same issue. The reason is that the binary is the same in this case, therefore there is no...

As I understand from @mikeizbicki's comments in #60 the issue there was code generation being different when the source code was actually changed. The code generated was more efficient in...

I fixed this in gauge: https://github.com/vincenthz/hs-gauge/pull/3. It can be pulled from there. The fix runs each benchmark in a separate process. However the root cause seems to be space hold...

It seems it is not very uncommon. I have hit the same issue: https://github.com/composewell/streamly/pull/1100/checks?check_run_id=2819329899 . I reached the same conclusion that it might be coming from the cache, tried bumping...

It worked when I changed the cabal version 3.4 to 3.2.

It worked with clearing the cache too, earlier I made a mistake so the cache was not cleared.

I would appreciate any help in doing that. A PR is welcome. BTW, the charts in the readme are not all that is available in the package. It has benchmarks...