4 ms·

Can you try https://github.com/adamritter/fastgron https://github.com/adamritter/fastgron as a comparision?

• zimpenfish 3y ago
  `fastgron`: 8.5s 2.2G resident edit: Interestingly whilst doing this test, I piped the output into `fastgron -u` (39.5G resident) and `jq` rejected that. Will have to investigate further but it's a bit of a flaw if it can't rehydrate its own output into valid JSON.
  • xiphias2 3y ago
    Thanks, it's a clear bug. I created a new issue for it: https://github.com/adamritter/fastgron/issues/19 https://github.com/adamritter/fastgron/issues/19
  • xiphias2 3y ago
    I released fastgron v0.7.5 which contains fixed in string escaping. Could you please take another look?
    • zimpenfish 3y ago
      Already commented on the github issue but will have another look, yep.
      • xiphias2 3y ago
        Sure, I saw it, thanks! I fixed the semicolon bug, but of course correctness is more important.
        • zimpenfish 3y ago
          Update for anyone following - 0.7.6 recreates my 800MB input JSON correctly after trip through `fastgron | fastgron -u` which is good work.