blocks|key|789922|text|看看kryo吧。它比内置的序列化机制快得多(它写出了很多字符串，并且严重依赖于反射)，但使用起来有点困难。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|789923|编辑:下面的R.Moeller推荐了FST，我之前从未听说过它，但看起来比kryo更快，而且与java内置序列化兼容(这应该会使它更容易使用)，所以我看一下第一个|789924|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/EsotericSoftware/kryo|1|http://ruedigermoeller.github.io/fast-serialization/^0|2|4|0|0|I|3|1|0^^$0|@$1|2|3|4|5|6|7|P|8|@]|9|@$A|Q|B|R|1|S]]|C|$]]|$1|D|3|E|5|6|7|T|8|@]|9|@$A|U|B|V|1|W]]|C|$]]|$1|F|3|-4|5|6|7|X|8|@]|9|@]|C|$]]]|G|$H|$5|I|J|K|C|$L|M]]|N|$5|I|J|K|C|$L|O]]]]

have a look at <a href="https://github.com/EsotericSoftware/kryo" rel="noreferrer">kryo</a>.
its much much faster than the built-in serialization mechanism (that writes out a lot of strings and relies heavily on reflection), but a bit harder to use.
 
edit: R.Moeller below suggested <a href="http://ruedigermoeller.github.io/fast-serialization/" rel="noreferrer">FST</a>, which i've never heard of until now but looks to be both faster than kryo and compatible with java built-in serialization (which should make it even easier to use), so i'd look at that 1st

blocks|key|4139943|text|您可能还想看看FST。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|4139944|还提供了用于离堆读写的工具|4139945|entityMap|0|LINK|mutability|MUTABLE|url|http://ruedigermoeller.github.io/fast-serialization/^0|7|3|0|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@$A|O|B|P|1|Q]]|C|$]]|$1|D|3|E|5|6|7|R|8|@]|9|@]|C|$]]|$1|F|3|-4|5|6|7|S|8|@]|9|@]|C|$]]]|G|$H|$5|I|J|K|C|$L|M]]]]

You might also want to have a look at <a href="http://ruedigermoeller.github.io/fast-serialization/" rel="noreferrer">FST</a>.

also provides tools for offheap reading/writing

blocks|key|4622326|text|尝试使用Google+protobuf或Thrift。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|4622327|entityMap|0|LINK|mutability|MUTABLE|url|https://developers.google.com/protocol-buffers/docs/javatutorial|1|http://thrift.apache.org/^0|4|F|0|K|6|1|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@$A|O|B|P|1|Q]|$A|R|B|S|1|T]]|C|$]]|$1|D|3|-4|5|6|7|U|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]|L|$5|G|H|I|C|$J|M]]]]

Try <a href="https://developers.google.com/protocol-buffers/docs/javatutorial">Google protobuf</a> or <a href="http://thrift.apache.org/">Thrift</a>.

blocks|key|4139711|text|标准序列化添加了许多类型信息，然后在反序列化对象时对其进行验证。当您知道要反序列化的对象的类型时，通常不需要这样做。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4139712|您可以为每个类创建自己的序列化方法，它只是将对象的所有值写入一个字节缓冲区，并创建一个构造函数(或工厂方法，当您以这种方式摆动时)，它接受这样一个字节缓冲区并从其中读取所有变量。|4139713|但就像AlexR一样，我想知道你是否真的需要它。序列化通常只在数据离开程序时才需要(比如存储在磁盘上或通过网络发送到另一个程序)。|4139714|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

The standard serialization adds a lot of type information which is then verified when the object is deserialized. When you know the type of the object you are deserializing, this is usually not necessary.

What you could do, is create your own serialization method for each class, which just writes all the values of the object to a byte buffer, and a constructor (or factory method, when you swing that way) which takes such a byte buffer and reads all the variables from it.

But just like AlexR I wonder if you really need that. Serialization is usually only needed when the data leaves the program (like getting stored on disk or sent over the network to another program).

blocks|key|4622318|text|众所周知，Java的标准序列化速度很慢，并且在磁盘上使用大量的字节。这是非常简单的做你自己的自定义序列化。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4622319|javas+std序列化对于演示项目是很好的，但由于上述原因，不太适合专业项目。进一步的版本控制不在你的控制之下。|4622320|java提供了定制序列化所需的一切，请参阅我的帖子中的演示代码|4622321|Java+partial+(de)serialization+of+objects|offset|length|4622322|使用这种方法，您甚至可以指定二进制文件格式，这样在C或C#中它也可以被读入。定制序列化对象的另一个优点是比在主存中需要更少的空间(布尔值在主内存中需要4个字节，但在定制序列化时只需要1个字节(作为字节))|4622323|如果不同的项目合作伙伴必须读取您的序列化数据，Googles+Protobuf是一个可供选择的选择。|4622324|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/questions/13650457/java-partial-deserialization-of-objects/13650819#13650819^0|0|0|0|0|15|0|0|0|0^^$0|@$1|2|3|4|5|6|7|V|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|W|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|X|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|Y|8|@]|9|@$H|Z|I|10|1|11]]|A|$]]|$1|J|3|K|5|6|7|12|8|@]|9|@]|A|$]]|$1|L|3|M|5|6|7|13|8|@]|9|@]|A|$]]|$1|N|3|-4|5|6|7|14|8|@]|9|@]|A|$]]]|O|$P|$5|Q|R|S|A|$T|U]]]]

Java's standard serialisation is known to be slow, and to use a huge ammount of bytes on disk. It is very simple to do your own custom serialisation. 
javas std serialisation is nice for demo project but for above reasons not well suited for professional projects. Further versioning is not well under your controll. 

java provides all you need for custom serialisation, see demo code in my post at

<a href="https://stackoverflow.com/questions/13650457/java-partial-deserialization-of-objects/13650819#13650819">Java partial (de)serialization of objects</a>

With that approach you even can specify the binary file format, such that in in C or C# it could be read in, too.
Another advantage custom setialized objects need less space than in main memory (a boolean needs 4 byte in main memm but only 1 byte when custom serialized (as byte)

If differnet project partners have to read your serialied data, Googles Protobuf is an alternative to look at.

Suppose I use the standard Java object serialization to write/read small (&lt; 1K) Java objects to/from memory buffer. The most critical part is the deserialization, i.e. reading Java objects from memory buffer (byte array).

Is there any faster alternative to the standard Java serialization for this case ?

Java serialization alternative with better performance

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

教程

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云智能顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

EdgeOne AI 安全实战专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

聚焦“写作效率、视觉美观与运行性能”三方面进行全面升级，为您提供更高效、稳定的创作环境

社区富文本&Markdown编辑器全新改版上线，欢迎大家体验!

诚挚邀请您参与本次调研，分享您的真实使用感受与建议。您的反馈至关重要，感谢您的支持与参与！

社区新版编辑器体验调研

假设我使用标准Java对象序列化在内存缓冲区中写入/读取小(< 1K) Java对象。最关键的部分是反序列化，即从内存缓冲区(字节数组)读取Java对象。对于这种情况，有没有比标准Java序列化更快的选择呢？

问性能更好的Java序列化替代方案
EN

回答 5

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问性能更好的Java序列化替代方案EN

回答 5

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问性能更好的Java序列化替代方案
EN