From: Jon Harrop <jon@ffconsultancy.com>
To: David MENTRE <dmentre@linux-france.org>, caml-list@inria.fr
Subject: Re: [Caml-list] Parallelized parsing
Date: Tue, 21 Apr 2009 17:04:36 +0100 [thread overview]
Message-ID: <200904211704.36455.jon@ffconsultancy.com> (raw)
In-Reply-To: <3d13dcfc0904210019x1f624bebv82855519b0885050@mail.gmail.com>
On Tuesday 21 April 2009 08:19:33 you wrote:
> On Mon, Apr 20, 2009 at 23:15, Jon Harrop <jon@ffconsultancy.com> wrote:
> > For example, Mathematica syntax for nested lists of integers looks like:
> >
> > {{{1, 2}}, {{3, 4}, {4, 5}}, ..}
> >
> > and there are obvious divide-and-conquer approaches to lexing and parsing
> > that grammar. You can recursively subdivide the string (e.g. memory
> > mapped from a file) to build a tree of where the tokens { , and } appear
> > by index and then recursively convert the tree into an AST.
> >
> > What other grammars can be lexed and/or parsed efficiently in parallel?
>
> Is it of any use? The overhead of parsing a single file in parallel is
> so high that you won't have any speedup, especially compared to the
> much simpler approach of parsing *several* files in parallel.
I'm seeing near-linear speedups parsing nested Mathematica lists in F# using
the algorithms I described. Moreover, dumping large quantities of data from
Mathematica in that format is much easier than dividing it into separate
files because there is no clear break in the tree.
--
Dr Jon Harrop, Flying Frog Consultancy Ltd.
http://www.ffconsultancy.com/?e
prev parent reply other threads:[~2009-04-21 15:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-20 21:15 Jon Harrop
2009-04-20 21:35 ` [Caml-list] " Mike Lin
2009-04-21 0:52 ` Yitzhak Mandelbaum
2009-04-21 15:55 ` Jon Harrop
2009-04-21 1:44 ` Polymorphism problem Eliot Handelman
2009-04-21 8:50 ` [Caml-list] " Mauricio Fernandez
2009-04-21 7:19 ` [Caml-list] Parallelized parsing David MENTRE
2009-04-21 16:04 ` Jon Harrop [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200904211704.36455.jon@ffconsultancy.com \
--to=jon@ffconsultancy.com \
--cc=caml-list@inria.fr \
--cc=dmentre@linux-france.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox