which serialization frame should i choose?

[yan lambiel]

I should think about these aspects.

<1> good compatibility

<2> it could add and update or del field;

<3> support compression;

<4> low time and memory cost

The Optional item is Kryo .... Protostuff...... and so on;

hope your advice, thanks a lot

[Kannan Goundan]

Can you clarify your requirements?

1. What do you mean by "good compatibility"?

2. Why do you need to add/update/del fields?  Are you using this as a storage format or a message format?  What do you expect to happen when a field is deleted but older code expects the field to be present?

3. All serialized data can be run through a compression algorithm.  What kind of support do you want from the serialization library itself?

4. This benchmark might help you get a rough idea of performance, but it can also be misleading.

- This benchmark uses a specific schema.  Your schema will probably perform differently.

- We don't really measure memory footprint.

- We definitely don't measure cache footprint.

If there are multiple serializers that meet requirements 1-3, and if you have the time, you should try implementing a couple of them and compare the performance in your overall system.

--
You received this message because you are subscribed to the Google Groups "java-serialization-benchmarking" group.
To unsubscribe from this group and stop receiving emails from it, send an email to java-serialization-benchmarking+unsubscribe@googlegroups.com.
To post to this group, send email to java-serialization-benchm...@googlegroups.com.
Visit this group at https://groups.google.com/group/java-serialization-benchmarking.
For more options, visit https://groups.google.com/d/optout.

[yan lambiel]

thanks Kannan

1. good compatibility means api compatibility, backward compatibility

2. I using this as storage format. Older code expects the deleted field to be NULL when a field is deleted. The update scene the same as deleted

3. I hope the serialized frame support compression;

4. This benchmark url, could you give me?

在 2016年12月22日星期四 UTC+8下午8:55:59，Kannan Goundan写道：

[Kannan Goundan]

I still don't understand what you're looking for in requirements 1-3.

The benchmark URL: https://github.com/eishay/jvm-serializers/wiki

Don't take the numbers too seriously; the serializers differ in what they can do.

To unsubscribe from this group and stop receiving emails from it, send an email to java-serialization-benchmarking+unsu...@googlegroups.com.
To post to this group, send email to java-serialization-benchmarking...@googlegroups.com.

Visit this group at https://groups.google.com/group/java-serialization-benchmarking.
For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "java-serialization-benchmarking" group.

To unsubscribe from this group and stop receiving emails from it, send an email to java-serialization-benchmarking+unsu...@googlegroups.com.
To post to this group, send email to java-serialization-benchmarking...@googlegroups.com.