@Araq > Report it on github please
I'll fill a proper in issue on GH if useful. > but then I don't know how you measure it In short, I use `/usr/bin/time -f '%M %e' ./exe < input.json`. It gives * M: Maximum resident set size of the process during its lifetime, in Kilobytes. * e: Elapsed real (wall clock) time used by the process, in seconds. For a small file I get 1.5MB, for a multi-MB file, I get multi-MB consumed. It is pretty linear : about 3x the size of the input. I also tested with no mm, I get a constant overhead of 20%.
