Skip to content
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.

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

Fix blog title #2083

Merged
merged 1 commit into from
Aug 19, 2024
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions _posts/2024-08-19-quarkus-metaprogramming.adoc
Original file line number Diff line number Diff line change
@@ -1,9 +1,9 @@
---
layout: post
title: 'Leveraging Quarkus build-time metaprogramming capabilities to improve Jackson's serialization performance'
title: "Leveraging Quarkus build-time metaprogramming capabilities to improve Jackson's serialization performance"
date: 2024-08-19
tags: gizmo,jandex,jackson,performances
synopsis: 'Leveraging Quarkus build-time metaprogramming capabilities to improve Jackson's serialization performance'
synopsis: "Leveraging Quarkus build-time metaprogramming capabilities to improve Jackson's serialization performance"
author: mariofusco
---
:imagesdir: /assets/images/posts/metaprogramming
Expand Down Expand Up @@ -371,4 +371,4 @@ image::f3.png[]
In fact in this case all the objects serializations, the one of the `Customer` instance returned by the rest endpoint plus all other objects referenced by it, are now performed by the serializers generated during the deployment phase, the ones with the class names terminating in `$quarkusjacksonserializer` and evidenced in purple in this last flamegraph.

.Flamegraph of serialization demonstrating how all the necessary generated serializers are invoked
image::f4.png[]
image::f4.png[]