the buffer size needs to be fixed at compile
time. I'll make this change in the next major release.
John
From: Vasyl Pasternak vasyl.paster...@gmail.com
Subject: Re: [Haskell-cafe] Iteratee performance
To: Gregory Collins g...@gregorycollins.net
Gregory,
Thank you, your code helps, now my
Hi Cafe,
Yesterday I played with iteratee package, and wanted to check its
performance. I tried to count lines in a file, as Oleg in his famous
lazy_vs_correct[1] article. The results somewhat disappointed me.
The statistics and code follows, but shortly: lazy bytestring is the
fastest, iteratee
Am Mittwoch 17 März 2010 17:01:06 schrieb Gregory Collins:
Vasyl Pasternak vasyl.paster...@gmail.com writes:
Hi Cafe,
Yesterday I played with iteratee package, and wanted to check its
performance. I tried to count lines in a file, as Oleg in his famous
lazy_vs_correct[1] article. The
Gregory,
Thank you, your code helps, now my it runs in the speed of lazy
bytestring test but uses less memory with it.
I've only added to your code more strictness in the recursion, my
version is below.
BTW, I think it is more useful to let user set the chunk size for
reading, so I'd like to
On Wed, Mar 17, 2010 at 5:55 PM, Vasyl Pasternak
vasyl.paster...@gmail.com wrote:
BTW, I think it is more useful to let user set the chunk size for
reading, so I'd like to see this possibility in the iteratee package.
Indeed, this is also the way I designed my enumerator for usb bulk and
