Loading Profile...
Mac data collector takes up 50-80% CPU
If you want people to use this, you need to make sure it's as unobtrusive as possible, and that means DON'T take up 50+% of their CPU. It's rather ridiculous, I can't imagine it needs to do this much... every few seconds poll for the current application and/or website.
Granted my computer is already pretty slow (1.33GHz) but that's all the more reason it shouldn't be a CPU hog.
I'd really like to use RescueTime, but there's NO way I can use it in it's current state.
Granted my computer is already pretty slow (1.33GHz) but that's all the more reason it shouldn't be a CPU hog.
I'd really like to use RescueTime, but there's NO way I can use it in it's current state.
I’m frustrated
10
people have this problem
I have this problem, too!
Tell me when someone solves it.
The more people who report this problem, the more it gets noticed.
The more people who report this problem, the more it gets noticed.
The company has acknowledged this problem.
Create a customer community for your own organization
Plans starting at $19/month
-
Inappropriate?Running RescueTime on the Mac should only use 2-3% CPU even with your scan interval set to 1 second.
RescueTime relies on a number of Apple provided applications (System Events, URL Access Scripting, etc). We have seen situations where one of the dependent applications has crashed or is hanging and that might cause RescueTime to use more CPU. Also during log updates you might see RescueTime climb a bit, but typically I see less than 5% even when sending a large number of log files.
Have you tried quitting and restarting RescueTime to see if that resolves the issue? Or even more drastic, restarting the computer? If you are able to reproduce the issue consistently, I'd love to work with you to see if there is some configuration issue that RescueTime is not handling well on your system.
Thanks! -
Inappropriate?I did try restarting the app a couple times before my last post, but I tried again after and it's back to normal levels now. If it happens again I'll let you know.
I’m undecided
-
Inappropriate?I second this. RescueTime on my Mac reports upwards of 70% CPU a lot of times and the only way to make it work is restart RescueTime. This is consistent for me. First I thought it might be Firefox but a little monitoring using top shows Rescuetime as a culprit.
Also, it seems like the problem only occurs if I keep rescuetime running for a while. If I shut it down and restart it every so often, it seems to work ok.
Im on a MacBook Air with OSX Leopard.
I’m unconcerned
-
Inappropriate?Thanks for the update on this Sarat, I've setup a test system to try and reproduce this CPU usage issue.
The current RescueTime does not deal well with other applications that are not responding in a timely fashion. If you notice the CPU usage for RescueTime running high, check to also see if there is another application that is listed as "not responding" in the Activity Monitor. -
Inappropriate?Hi Joe,
I presumed so. It looks like Firefox 3 along with RescueTime is the culprit. The problem is that if I run Firefox 3 without having RescueTime on, I can't actually replicate this scenario, in that, the system never "slows down", although Firefox 3 does eat 30-40% CPU. -
Inappropriate?I'm having this problem as well, except it's 100% cpu and there's no apparent culprit. I quit all my programs, including resetting the Dock and the Finder, and still RescueTime is using 100% cpu according to both top and Activity Monitor. Also, according to Activity Monitor, there are no processes that aren't responding.
I have not reset RescueTime, so if there's any data you'd like let me know.
-
Inappropriate?I just reset it, but I'll keep an eye on it and see if I can reproduce the behavior.
-
Inappropriate?I get this same problem and I can trigger it to happen when I tell it to "Send update now". This happened to me a while ago (as in months ago) and I stopped using the tool. When I saw an update to the software I was hopeful, but clearly the problem persists.
The error that I see in the detailed logs while this is happening is:
2008-12-07 16:17:38
Sending file: '/Users/rgarver/Library/RescueTime/Logs/Pending/rt_20080721-154041.yml'
2008-12-07 16:17:43
Error: The command exited with a non-zero status. #255
The name of the yml file changes but it repeats the error each time.
I’m frustrated
-
Inappropriate?I'm having this problem too. I notice when my Mac's fans are running full throttle due to CPU being hogged for long periods of time. Will have to stop using RescueTime until it is fixed :-(
I’m frustrated
-
Inappropriate?Likewise: RescueTime basically takes up around 95% of one core at all times... It seems like when I first installed it was fine; then the slow-down started happening only occasionally (when posting updates back to RT?); now it's permanently chomping through the CPU.
I’m suffering from system slowdown
-
Inappropriate?I'm curious to see if removing the old log files and resetting the preferences helps with this issue.
Try the following:
- Perform a "Send Update Now" in RescueTime to send any pending log data
- After that is successful, Quit RescueTime
- Remove the following directories located at Macintosh HD:Users:[your username]:Library:RescueTime
- Logs
- Results (if it exists)
- Leave the Whitelists directory in place
- Remove the RescueTime preferences located at: Macintosh HD:Users:[your username]:Library:Preferences:com.RescueTime.plist
- Start RescueTime again, you will be prompted to enter your email and password -
Inappropriate?Joe,
I noticed RT's CPU usage ballooning again this morning, so followed your instructions. First impressions looked good, but shortly after the CPU spiked again.
Any other ideas?
Tim.
EMPLOYEE
