Oh! My email was a little confusing. Let me restate:
Screensharing using webRTC on Windows 8.1 on the server side* using google chrome: The tab which is running the JS takes around 8-10% cpu usage. GPU process shows 0%
Screensharing using webRTC on MAC OS X 10.8.5 on the server side* using google chrome: The tab which is running the JS takes around 30-50% cpu usage. GPU process shows 0%
CPU usage jumps up when there is activity on screen. I have reported <inactive screen CPU usage> - <active screen CPU usage>.
Server side: I have uni directional screen sharing so I call one of the peers server and one client.
@aaroncray
That is interesting. If I can make chrome/openGL use the GPU for video encoding then there won't be any CPU overhead for encoding. That makes sense. I will get back to this thread if I find a solution.