[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Qemu-devel] QEMU websockets support is laggy?
From: |
Daniel P. Berrange |
Subject: |
Re: [Qemu-devel] QEMU websockets support is laggy? |
Date: |
Fri, 27 Jan 2017 09:35:38 +0000 |
User-agent: |
Mutt/1.7.1 (2016-10-04) |
On Tue, Jan 24, 2017 at 05:02:25PM -0500, Brian Rak wrote:
> We've been considering switching over to using qemu's built in websockets
> support (to avoid the overhead of needing websockify running). We've been
> seeing very poor performance after the switch (it takes the console 4-5
> seconds to update after pressing a key). So far, I haven't been able to
> find any indication of why this is happening. The exact same configuration
> works perfectly when running with websockify, but laggy when hitting qemu
> directly.
>
> I've tried a few things (disabling encryption, bypassing our usual nginx
> proxy, even connecting via a ssh tunnel), and haven't made any sort of
> progress here. Has anyone else seen this? Any suggestions as to where I
> should start looking?
Can you clarify the exact setup you have ? As mentioned on IRC, I don't
see any degradation in performance betweeen builtin websockets vs a
websockets proxy - if anything the builtin websockets is marginally less
laggy. I was connecting over TCP localhost, however, so would not see
any effects of network latency. My test was QEMU git master, with noVNC
git master.
Regards,
Daniel
--
|: http://berrange.com -o- http://www.flickr.com/photos/dberrange/ :|
|: http://libvirt.org -o- http://virt-manager.org :|
|: http://entangle-photo.org -o- http://search.cpan.org/~danberr/ :|