From 5637a65d3c9457ffad364eb479ec642613904a75 Mon Sep 17 00:00:00 2001 From: George Gastaldi Date: Mon, 19 Aug 2024 10:43:35 -0300 Subject: [PATCH] Fix blog title --- _posts/2024-08-19-quarkus-metaprogramming.adoc | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/_posts/2024-08-19-quarkus-metaprogramming.adoc b/_posts/2024-08-19-quarkus-metaprogramming.adoc index 2282ef2c33b..3728a979908 100644 --- a/_posts/2024-08-19-quarkus-metaprogramming.adoc +++ b/_posts/2024-08-19-quarkus-metaprogramming.adoc @@ -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 @@ -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[] \ No newline at end of file +image::f4.png[]