MacOS - vncviewer: High CPU load due to writing the image to the screen #372

Open
fredowski opened this Issue Oct 25, 2016 · 2 comments

Projects

None yet

2 participants

@fredowski
Contributor
fredowski commented Oct 25, 2016 edited

Hi,

i looked at XCode Instruments to see where the CPU cycles are consumed in the vncviewer process. I wanted to check if I can see a difference in the jpeg vs. jpeg-turbo build. I see roughly 20% of the load going to jpeg decoding, while 80% is spend more or less in writing the image to the screen. So on Mac the jpeg decoding seems to be a minor problem compared to image writing. I run this on a MacBook Pro with HighResolution Display - so maybe something is converted there...

Here is a screenshot showing the Main Thread vs. one of the worker threads with jpeg decoding:
inst-overview

Here is the first part of the main thread:

inst1

and here is the remaining part.

inst2

60% of the total CPU power for vncviewer is spend in the OS routine: argb32_image_mark_RGB24.

Googling seems to show more problems with this: http://stackoverflow.com/questions/21665473/coregraphics-argb32-image-mark-rgb24-is-slow

Friedrich

--- Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/38734999-macos-vncviewer-high-cpu-load-due-to-writing-the-image-to-the-screen?utm_campaign=plugin&utm_content=tracker%2F3557444&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F3557444&utm_medium=issues&utm_source=github).
@CendioOssman CendioOssman added the bug label Oct 28, 2016
@CendioOssman
Member

Yes, I'm afraid this is a somewhat known issue. Unfortunately none of the suggested fixes we've found so far have worked.

@CendioOssman
Member

It also happens on all Macs, not just high resolution displays.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment