issue with VNC

[leeadh]

got this issue

Have you tried the x11vnc '-ncache' VNC client-side pixel caching feature yet?

The scheme stores pixel data offscreen on the VNC viewer side for faster
retrieval. It should work with any VNC viewer. Try it by running:

x11vnc -ncache 10 ...

One can also add -ncache_cr for smooth 'copyrect' window motion.
More info: http://www.karlrunge.com/x11vnc/faq.html#faq-client-caching

[storax]

Hi, thanks for raising an issue. I did not know about this particular feature yet.

However, it is not quite clear to me what specific issue you are experiencing with VNC.
Is the performance not good enough? Are you having trouble connecting with a viewer?
Or is this a suggestion to adopt these flags when kubedoom launches the VNC server?

Personally, I don't mind if kubedoom doesn't use the most optimized VNC setting. The main goal is for people to have fun with this project. I hope the way VNC is currently used doesn't impact that.

[cpressland]

@leeadh I'm currently exploring options for making this run faster as it's quite slow in our environment, multiple seconds of zero frames. Unfortunately the -ncache 10 feature resulted in pretty funny behaviour on macOS (See Screenshot). I'll see if I can make this behave itself and open a PR if I come up with something useful.