From: Markus Armbruster <armbru@redhat.com>
To: Bin Guo <guobin@linux.alibaba.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [PATCH] qobject/json-writer: preallocate output buffer
Date: Tue, 02 Jun 2026 10:34:43 +0200 [thread overview]
Message-ID: <87ldcx5oik.fsf@pond.sub.org> (raw)
In-Reply-To: <20260529023426.54680-1-guobin@linux.alibaba.com> (Bin Guo's message of "Fri, 29 May 2026 10:34:26 +0800")
Bin Guo <guobin@linux.alibaba.com> writes:
> json_writer_new() creates the output GString with g_string_new(NULL),
> which starts at the GLib default of 64 bytes. Serializing typical
> QMP responses then requires multiple reallocations as the buffer
> grows -- for query-qmp-schema the GString is reallocated 12+ times.
That's an extreme case. Most responses are *much* smaller. Still,
starting with a larger buffer makes sense.
> Preallocate JSON_WRITER_INITIAL_SIZE (4096) bytes. This covers
> most QMP responses without any reallocation. 4096 is one page on
> most systems, which is efficient for the allocator.
I doubt "one page" matters. How many QMP commands get executed in
practice? A couple of hundred during startup, then tens per second?
Probably less than that.
> The JSONWriter
> is a short-lived object so the preallocation does not accumulate.
>
> Signed-off-by: Bin Guo <guobin@linux.alibaba.com>
> ---
> qobject/json-writer.c | 5 ++++-
> 1 file changed, 4 insertions(+), 1 deletion(-)
>
> diff --git a/qobject/json-writer.c b/qobject/json-writer.c
> index aac2c6ab71..fb3f3f3e3c 100644
> --- a/qobject/json-writer.c
> +++ b/qobject/json-writer.c
> @@ -24,13 +24,16 @@ struct JSONWriter {
> GByteArray *container_is_array;
> };
>
> +/* Covers most QMP responses without reallocation (one page) */
Covering most responses matters, one page does not. Suggest
/* Should cover most QMP responses without reallocation */
> +#define JSON_WRITER_INITIAL_SIZE 4096
> +
> JSONWriter *json_writer_new(bool pretty)
> {
> JSONWriter *writer = g_new(JSONWriter, 1);
>
> writer->pretty = pretty;
> writer->need_comma = false;
> - writer->contents = g_string_new(NULL);
> + writer->contents = g_string_sized_new(JSON_WRITER_INITIAL_SIZE);
> writer->container_is_array = g_byte_array_new();
> return writer;
> }
Consider tweaking the commit message and the comment to address my
remarks.
Reviewed-by: Markus Armbruster <armbru@redhat.com>
next prev parent reply other threads:[~2026-06-02 8:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-29 2:34 [PATCH] qobject/json-writer: preallocate output buffer Bin Guo
2026-05-29 6:13 ` Philippe Mathieu-Daudé
2026-06-02 8:34 ` Markus Armbruster [this message]
2026-06-03 9:52 ` Daniel P. Berrangé
2026-06-03 10:24 ` Markus Armbruster
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87ldcx5oik.fsf@pond.sub.org \
--to=armbru@redhat.com \
--cc=guobin@linux.alibaba.com \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.