Re: Design/structure X3 parser more like Qi parser
Larry Evans <[email protected]>
| Newsgroups | gmane.comp.parsers.spirit.general |
|---|---|
| Message-ID | <[email protected]> |
On 12/13/2016 11:56 AM, Seth wrote: [snip] > > Hope this helps someone spot an improvement/cause of the poor performance. > > Cheers, > Seth Seth, and anyone else who might be interested in helping find the cause of the poor performance, I've uploaded: summary.chrono-csv-*.out to: https://github.com/cppljevans/spirit/tree/develop/workbench/x3/csv_parser which shows that at -O0, x3 performs better, but as the optimization increases, qi begins to perform better. Since the crossover of performance occurs between -O0 and -O1 for the gcc compiler, I also uploaded profile's for those to optimization's for gcc to: https://github.com/cppljevans/spirit/blob/develop/workbench/x3/csv_parser/gprof-csv-x3_ns_rdef-spirit-GET0-XRULE0-OptO0-gcc6_20151018.flat_graph https://github.com/cppljevans/spirit/blob/develop/workbench/x3/csv_parser/gprof-csv-x3_ns_rdef-spirit-GET0-XRULE0-OptO1-gcc6_20151018.flat_graph At the moment, based on the contents of those files, I'm unable to discern any likely cause of the poor performance. I'm hoping that someone reading this, with more experience with and understanding of gprof, could infer some likely cause of the poor performance. If so, maybe they could suggest some change to improve the performance which I would gratefully implement and report back here with the results. -regards, Larry ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, SlashDot.org! http://sdm.link/slashdot