Skip to content

KryoSerializer is more space consuming than JDKSerializer? #118

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Closed
a1364533187 opened this issue Apr 21, 2021 · 1 comment · Fixed by #235
Closed

KryoSerializer is more space consuming than JDKSerializer? #118

a1364533187 opened this issue Apr 21, 2021 · 1 comment · Fixed by #235

Comments

@a1364533187
Copy link

a1364533187 commented Apr 21, 2021 •
edited
Loading

In class KryoSerializer, I see the comments about SerializeUtil with Kryo, which is faster and more space consuming., but when I read this article https://www.shenyanchao.cn/blog/2019/02/13/redis-serializer/, it looks like KryoSerializer is faster and less space consuming.

se
article reference: https://www.shenyanchao.cn/blog/2019/02/13/redis-serializer/
@hazendaz hazendaz mentioned this issue Nov 22, 2023
Merged
hazendaz added a commit that referenced this issue Nov 22, 2023
@hazendaz
Merge pull request #235 from hazendaz/master
0c0eb0c 
[ci] Correct kryo statement to mean uses less space - fixes #118
@hazendaz
Copy link
Member

sorry didn't see this previously as this project isn't monitored that closely, you are correct, I've fixed it to state 'less space consuming'.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

[ci] Correct kryo statement to mean uses less space - fixes #118 hazendaz/redis-cache
2 participants
@hazendaz @a1364533187