[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [PATCH v3 2/4] python/qmp: increase read buffer size
From: |
Daniel P . Berrangé |
Subject: |
Re: [PATCH v3 2/4] python/qmp: increase read buffer size |
Date: |
Wed, 9 Nov 2022 10:59:59 +0000 |
User-agent: |
Mutt/2.2.7 (2022-08-07) |
On Wed, Nov 09, 2022 at 09:39:14AM +0000, Daniel P. Berrangé wrote:
> On Tue, Nov 08, 2022 at 03:38:21PM -0500, John Snow wrote:
> > On Thu, Nov 3, 2022 at 6:29 AM Maksim Davydov
> > <davydov-max@yandex-team.ru> wrote:
> > >
> > > After modification of "query-machines" command the buffer size should be
> > > more than 452kB to contain output with compat-props.
> > >
> > > Signed-off-by: Maksim Davydov <davydov-max@yandex-team.ru>
> > > Reviewed-by: Vladimir Sementsov-Ogievskiy <vsementsov@yandex-team.ru>
> > > ---
> > > python/qemu/qmp/qmp_client.py | 4 ++--
> > > 1 file changed, 2 insertions(+), 2 deletions(-)
> > >
> > > diff --git a/python/qemu/qmp/qmp_client.py b/python/qemu/qmp/qmp_client.py
> > > index 5dcda04a75..659fe4d98c 100644
> > > --- a/python/qemu/qmp/qmp_client.py
> > > +++ b/python/qemu/qmp/qmp_client.py
> > > @@ -197,8 +197,8 @@ async def run(self, address='/tmp/qemu.socket'):
> > > #: Logger object used for debugging messages.
> > > logger = logging.getLogger(__name__)
> > >
> > > - # Read buffer limit; large enough to accept query-qmp-schema
> > > - _limit = (256 * 1024)
> > > + # Read buffer limit; large enough to accept query-machines
> > > + _limit = (512 * 1024)
> >
> > wow :)
>
> Meanwhile over in python/qemu/qmp/protocol.py the read buffer limit is
> set to just 64 kb.
>
> If the current output of a particular command is known to 450 kb, then
> setting this limit to 512 kb is waaaaaaay to conservative, and we'll
> inevitably have to change it again when someone finds the next command
> that overflows.
>
> Recall this thread
>
> https://lists.gnu.org/archive/html/qemu-devel/2022-09/msg01060.html
>
> In fact, let me be the someone who demonstrates a real case where 512kb
> is not enough....
Another example...
Create a guest with 255 vCPUs (current RHEL downstream vCPU limit),
and run
{"execute":"query-stats","arguments":{"target": "vcpu"}}
it'll get back a 0.38 MB QMP reply. RHEL raised the limit to 710
vCPUs, giving a little over 1 MB QMP reply. There is a strong desire
to go even higher. With 4096 vCPUs it'd get an ~6 MB QMP reply.
With regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
[PATCH v3 1/4] qom: add default value, Maksim Davydov, 2022/11/03
[PATCH v3 3/4] qmp: add dump machine type compatible properties, Maksim Davydov, 2022/11/03