Rather than focusing on scaling serialization, changing architecture might be more appropriate (using a stream based serializer, removing redundant data by using references of some kind (even if in userland), etc.). Often times when we want to share data between things for v8 (I'm assuming out of process / Isolate) we are going to hit a wall not by the serialization, but the raw limitation of computing. IE: dictionary construction time. It may not help you serialize things faster, but a leaner architecture might be a solution for you, especially if you can isolate out data that can be processed parallel without relying on each other. Without knowing more about the problem, I cannot comment beyond that.
-- v8-users mailing list [email protected] http://groups.google.com/group/v8-users
