vincent163

After resuing the parser, here are the new benchmark results: ``` goos: linux goarch: amd64 pkg: github.com/valyala/fastjson BenchmarkParse/small/stdjson-map-4 300000 4660 ns/op 40.77 MB/s 960 B/op 51 allocs/op BenchmarkParse/small/stdjson-struct-4 1000000 2362...

In fact, this will also improve performance by avoiding the copy. The benchmarks are here: https://gist.github.com/hewenyang/91618e54342f65809f4cb3c9c3aa1240 The observation is based on the `canada` benchmark which has the largest memory consumption....

> I'm aware of the possible memory leak, but couldn't find good solution yet. Straightforward zeroing of all the pointers on Reset slows down the Parser on on JSONs with...

Oh, I missed something. The creation timestamp still contains enough fingerprint even if randomized. Looks like we need a ZKP system to prove the timestamp. Don't know if it's possible.

> > but on my machine it seems that the bottleneck has already moved from Python to MySQL > > I am pretty sure that the real bottleneck is the...

> Here, we guarantee that no matter the environment or whatever `f` does, _if_ the stack frame of `test` ever gets popped or otherwise "deallocated", then the `println!` certainly happens....