[Haskell-cafe] parsec2 vs. parsec3... again
Maciej Piechotka
uzytkownik2 at gmail.com
Thu Jan 13 10:03:41 CET 2011
On Wed, 2011-01-12 at 18:15 -0800, Evan Laforge wrote:
> On Mon, Dec 27, 2010 at 6:51 AM, Evan Laforge <qdunkan at gmail.com>
> wrote:
> >> I've uploaded attoparsec-text and attoparsec-text-enumerator to
> >> Hackage. I've written those packages late last week and asked for
> >
> > Very nice! I'll download this and try it out. Attoparsec has a bit
> > different combinators than parsec so it'll take some rewriting, but
> > it's work I'd have to do anyway to try the bytestring+attoparsec
> > approach.
>
> Well, I tried it... and it's still slower!
>
> parsec2, String: (a little faster since last time since I have new
> computer)
> total time = 9.10 secs (455 ticks @ 20 ms)
> total alloc = 2,295,837,512 bytes (excludes profiling
> overheads)
>
> attoparsec-text, Data.Text:
> total time = 14.72 secs (736 ticks @ 20 ms)
> total alloc = 2,797,672,844 bytes (excludes profiling
> overheads)
Sorry for asking but just for reference - what is performance of
nanoparsec on your machine in this test?
Regards
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 836 bytes
Desc: This is a digitally signed message part
URL: <http://www.haskell.org/pipermail/haskell-cafe/attachments/20110113/6d7ef8eb/attachment.pgp>
More information about the Haskell-Cafe
mailing list