Submit Hint Search The Forums LinksStatsPollsHeadlinesRSS
14,000 hints and counting!

Speed up by disabling Screen Sharing System
I am trying to squeeze some more speed out of my Mac, as it is necessary for me to also use a Windows emulator on it.

I have tried to clean up things, and I noticed that when I turned off the three following launchd processess, with the free utility Lingon, at least it appeared to run marginally faster.
  • Start Lingon (google Lingon downloads).
  • Find the processes listed below in the lowest three groups in Lingon's sidebar.
  • Select, Disable, Save, and Confirm with your Administrator password for each of them.
com.apple.RFBEventHelper 
com.apple.RFBRegisterMDNS_ScreenSharing.server
com.apple.RFBRegisterMDNS_RemoteManagement.server
Then you notice slightly better performance with screen updating and the like.

[crarko adds: I haven't tested this one. I use Screen Sharing all the time. I notice that the current version of Lingon has moved to the Mac App Store.]
    •    
  • Currently 2.50 / 5
  You rated: 4 / 5 (10 votes cast)
 
[7,029 views]  

Speed up by disabling Screen Sharing | 11 comments | Create New Account
Click here to return to the 'Speed up by disabling Screen Sharing' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
Speed up by disabling Screen Sharing
Authored by: zeniam1 on Mar 25, '11 07:49:58AM

Hmmm. And these are not disabled via the Sharing pane in System Preferences? Running launchctl, I don't see them listed. But perhaps I'm seeing what you are in your system.



[ Reply to This | # ]
Speed up by disabling Screen Sharing
Authored by: da2357 on Mar 25, '11 08:33:19AM
The three plists referenced are all system daemons that launch the following:

/System/Library/CoreServices/RFBEventHelper.bundle/Contents/MacOS/RFBEventHelperd /System/Library/CoreServices/RemoteManagement/AppleVNCServer.bundle/Contents/Support/RFBRegisterMDNS /System/Library/CoreServices/RemoteManagement/AppleVNCServer.bundle/Contents/Support/RFBRegisterMDNS

Since the three items are system daemons, you need to be root in order for 'launchctl list' to list them. One my Mac, at this moment, if I run:
[ ~ ]$ ps -ax | grep com.apple.RFBEventHelper
  958 ttys000    0:00.00 grep com.apple.RFBEventHelper
[ ~ ]$ ps -ax | grep com.apple.RFBRegisterMDNS_ScreenSharing.server
  960 ttys000    0:00.00 grep com.apple.RFBRegisterMDNS_ScreenSharing.server
[ ~ ]$ ps -ax | grep com.apple.RFBRegisterMDNS_RemoteManagement.server
  962 ttys000    0:00.00 grep com.apple.RFBRegisterMDNS_RemoteManagement.server
I get the PIDs of these three processes. I suppose one could write a simple bash script that would find the PID of these three processes on-demand and then kill them.

[ Reply to This | # ]
Speed up by disabling Screen Sharing
Authored by: Kalak on Mar 25, '11 09:27:07AM
Those are the PIDs of the grep statement, not the processes you're looking for. You should look at the tip and discussion on Ignoring grep self matching found here
---
--
Kalak
I am, and always will be, an Idiot.


[ Reply to This | # ]
Speed up by disabling Screen Sharing
Authored by: sdunster on Mar 25, '11 07:51:50AM

I don't see why you wouldn't just turn Screen Sharing off in Sharing preferences...



[ Reply to This | # ]
Speed up by disabling Screen Sharing
Authored by: lsequeir on Mar 25, '11 08:19:33AM

The best way that I can think of to get better performance when running windows alongside mac os x is to up your ram.
Each of the 2 concurrently running OSes requires a lot of ram. The required swapping when running windows 7 in Parallels Desktop used to bring my mac to its knees. After upping the ram to 8GB, it can run them both with aplomb.

---
Luís



[ Reply to This | # ]
Speed up by disabling Screen Sharing
Authored by: da2357 on Mar 25, '11 10:02:37AM
Thanks 'Kalak' for pointing out the error. I checked out the page you referenced and think I've correctly re-written the bash script:
#!/bin/bash
#
processOne=`ps -acx | grep [c]om.apple.RFBEventHelper | cut -c 2-5`
kill $processOne
#
processTwo=`ps -acx | grep [c]om.apple.RFBRegisterMDNS_ScreenSharing.server | cut -c 2-5`
kill $processTwo
#
processThree=`ps -acx | grep [c]om.apple.RFBRegisterMDNS_RemoteManagement.server | cut -c 2-5`
kill $processThree
exit 0
Comments and corrections welcome!

[ Reply to This | # ]
Speed up by disabling Screen Sharing
Authored by: jaydisc on Mar 25, '11 01:51:32PM

Killing a process managed by a launchd job will merely cause the process to be relaunched. So this script, and hint, are both bad ideas.

Just turn off Screen Sharing!!!



[ Reply to This | # ]
Speed up by disabling Screen Sharing
Authored by: MacUser06 on Mar 26, '11 03:12:42AM

Hello.

I just want add that screen sharing was turned off in the preference pane.

I think those processes are running whether you have screen sharing enabled or not.

I have 8 gigs of memory. I give 4 of them to parallells. but still If just leave parallells open, or work for a long time, (at least with parallells 5), then eventually things would bog down.)

I think disabling the three daemons really does some difference, when it comes to speed.

The other trick for getting more juice while running parallels with windows windows 7, is to use the "good GPU" if you got one. Then I think the aero technology of windows 7 kicks in.



[ Reply to This | # ]
Speed up by disabling Screen Sharing
Authored by: dezzie on Mar 26, '11 03:39:24AM

The plists are indeed loaded into launchd, regardless whether Screen Sharing is enable or not. However, the actual daemons are only running if Screen Sharing is enabled.



[ Reply to This | # ]
Speed up by disabling Screen Sharing
Authored by: jaydisc on Mar 26, '11 09:37:41PM

If Remote Management is enabled, the same processes might be running, as Screen Sharing is a subset of Remote Management. In my case, with Remote Management active, com.apple.RFBEventHelper was in my process list, and once I disabled Remote Management, it no longer was.



[ Reply to This | # ]
Not so much a hint, but more Wishful thinking.
Authored by: e_whizz on Mar 30, '11 05:20:04AM

Not so much a hint, but more Wishful thinking.

"Yeah, lets find some processes that seem to be related to screen refreshing or similar and kill them dead. Then ooh that was satisfying, I think it even sped things up a bit, yeah I'm sure of it, of course it would have, wouldn't it?"

That's the thought train here, without that last check.

Where is the science in this claim? No measurements before or after. No real indication of how much it was sped up, even as a real rough estimate.


I'll put this down to one of those 'hints' that just slipped through without much vetting. I mean, how useful is this really?


The most this could have sped your situation up by would not even get onto the left side of the decimal point in percentage terms.
Best to get more RAM and a speedy SSD RAID setup for any real tangible performance gains.

Edited on Mar 30, '11 05:22:26AM by e_whizz



[ Reply to This | # ]