Christopher Mooney
Christopher Mooney
Not sure I will get a chance to look at this in the coming days (perhaps even weeks), but here is what I suggest to find the cause. This is...
also: https://github.com/pgriess/node-msgpack/issues/26
Just looked at this, and I am going to need a more rich testing environment where I can easily run older versions of node and compile older versions of msgpack...
I merged a pull request into master that uses a O(1) heuristic (based on native JS msgpack implementation) that uses 512 depth check to check for cycles. This sped things...
Here are the new ratios: msgpack pack: 3398 ms msgpack unpack: 1453 ms json pack: 871 ms json unpack: 435 ms msgpack pack: 3549 ms msgpack unpack: 1478 ms json...
looks like the node JSON code is still ~4 times as fast.
@chakrit, First I wanted to say, this entire discussion is about the performance of node-msgpack in relation to the v8's JSON serialization functions. Most of my tests have been with...
@imax36581, can you let me know if you still have this problem? I just updated node-msgpack to 0.2.2, but did not specifically observe this problem.
I removed the old stream tests, as they are now hopelessly broken.
Yeah, this should be solved with one of the BigInt packages. I'm very busy, but would be happy to take a PR.