Hmm, a grammar will usually build a data structure that takes much more memory that the original text file, but it sounds a bit excessive to me that a 2-MB file would imply a 33 GB memory foot print, that's really a huge difference.

My second point is that, from a quick look, your file looks pretty regular, I am not sure that a full-fledged grammar is really required (understand me, I am really in favor of using real parsers as soon as the input gets a bit complicated in terms of positions of tokens and the like, but here, I am not totally convinced that it is not overkill or over-engineering). From a quick glance at your data, I would probably have a couple of regexes to get rid of comments and then parse it manually using the semi-colon as a separator.

But that's only a personal opinion, I did not take the time to analyze your grammars in any detail and I have no idea of what you are really trying to do with this data, so I may be completely wrong. This was just premature guts feeling after a very brief look at your problem, it could be that just working an hour or two on it would lead me to a very different conclusion.

Please also note that I know a very little bit about Regexp::Grammars, but next to nothing about Marpa.

In reply to Re: Grammar based parsing methodology for multi MB strings/files (Marpa::R2/Regexp::Grammars) by Laurent_R
in thread Grammar based parsing methodology for multi MB strings/files (Marpa::R2/Regexp::Grammars) by tj_thompson

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.