Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
I'm seeing 10x character size of the serialization of the initial DOM state (
I'm thinking that it could be reduced as follows:
Are there any strong reasons not to do any of the above?
I believe there is a huge potential to reduce the size of the recorded events(I always seeing 90% size reduction when I gzip the events).
So the works for reducing size may contain the following part:
Some pack/unpack strategies I know including:
Sorry for the later.
I think this issue is the most important one in the current stage, and I would like to provide a solution int the next major release.
With the ideas that I illustrated above, I have done some POC code in this repo.
Currently, I have implemented a analyze framework and several packers:
Now the msgpack packer is not working as intend and I'm still checking my implementation. The other two shows some good result when testing on two real-world events log.
I'm using two real-world events log to benchmark the packers: