Hardware Accelerated Video?
Does LMI Central use hardware acceleration for encoding/decoding the video stream, and is the codec published? I can only really speak anecdotally, but I feel like the CPU and GPU usage attribut...
Forum Discussion
I ended up having a little time to tool around tonight. Possibly some interesting findings:
On my host computer with the "Blank Screen" option enabled , and the "Display Accelerator" enabled, and nothing running on the host other than task manager (and LMI):
- LMI Remote Control Application process is using about 8-9% CPU and 0% GPU
- Desktop Window Manager process is using ~5-6% CPU and ~18-22% GPU
On my host computer with the "Blank Screen" option disabled , and the "Display Accelerator" enabled, and nothing running on the host other than task manager (and LMI):
- LMI Remote Control Application process is using about 0-3% CPU and 0-8% GPU. 0.3% GPU when fully idling, or up to 8% GPU when there is more motion on the host screen.
- Desktop Window Manager process is using ~0% CPU and ~0% GPU
I tried turning "Display Accelerator" off and rebooting the host and testing again. The CPU and GPU usage percentages were still the same as above (both when Blank Screen on and Black Screen off).
On my client computer with the "Blank Screen" option enabled , and nothing running on the host other than task manager (and LMI):
- LogMeIn Client process is using about 10-18% CPU and ~0% GPU
- Client Server Runtime process is using about ~0% CPU and 10-25% GPU (mostly around ~18% GPU, and only momentary spikes to ~25% GPU when there is a lot of motion on the host screen)
- Desktop Window Manager process is using ~2% CPU and ~0% GPU
On my client computer with the "Blank Screen" option disabled , and nothing running on the host other than task manager (and LMI):
- LogMeIn Client process is using about 1-8% CPU and ~0% GPU
- Client Server Runtime process is using about ~0% CPU and 0-15% GPU (mostly around ~0.5% GPU, and only momentary spikes to ~15% GPU when there is a lot of motion on the host screen)
- Desktop Window Manager process is using ~0% CPU and ~0% GPU
So it seems like it is "Blank Screen" which is comparably very resource-intensive - somehow on both the host and the client. So are there some hardware properties/specs which would be more optimized for use with "Blank Screen"?
etb thanks for sharing your input with the Community, as others are finding it helpful. 😊
You can find the minimum requirement for Screen blanking here. Otherwise, could you let me know a bit more about what you are thinking on hardware properties/specs that would be more optimized for use with "Blank Screen"?
Hi KateG ,
Thanks for not giving up on me yet - I know that walls of text can be brutal 🙂
I don't mean to overexplain this, because I'm definitely very far from an expert, and I could be wrong about details. But basically I'm drawing the parallel to hardware-accelerated video encoding and decoding.
An example with which we might be more familiar is like watching videos from the internet. If you would pull an old laptop off the shelf and watch a video, you might find that playing the video uses like 25%+ of CPU and kills the battery quickly. A more modern laptop would have a much easier time playing that same video. The reasons the modern laptop would be so much more efficient with playing the video are many, but one big reason is that the modern laptop would likely have hardware-accelerated video decoding such as Intel Quick Sync, or Nvidia NVDEC, etc. As long as the software being used supports using hardware acceleration, and as long as the hardware supports the codec in use, the specialized hardware can be used to very efficiently decode the video (low CPU/GPU usage).
So, tying it back to my question here: is there some particular hardware which can run Screen Blanking notably more efficiently - similar to how hardware with Quick Sync or NVDEC can play videos much more efficiently? Maybe the GoTo developers might say that LMI is using a certain codec, or that Screen Blanking is most optimized for a certain API, and so therefore a particular generation of graphics cards (or newer) would run things notably more efficiently?
Well, Screen Blanking on the Host side seems to have fixed the problem for at least one more laptop.
Still waiting to gain access to the rest.
Hi etb thanks for working with me as well!
From what I've learned so far a graphics card or codec won't apply, Screen Blanking is dependent on the Windows OS, which could be contributing to why it's resource intensive.We are checking with the product team for their input. I will update the thread when I learn more.
