Loading Profile...
Real work in background process should be logged
RescueTime watches what application window has focus, but what about tracking what process is using CPU cycles? When I'm working, sometimes I start a long-running process and then browse a couple websites while waiting for the process to finish. I'm still working, but I'm also filling in my time instead of just going idle or otherwise killing time. A feature like this would probably need a tuning option, but it could default to watch any process that is consistently over 15% - 20% of the CPU, indicating a background process that is doing work. How you would work this into your reporting is a little more complicated. Maybe if the background process acts as an over-ride, so if any tagged background process is using a high CPU percent then the foreground window would be ignored or otherwise discounted. The key would be the tagging. An untagged high-cycle background process (like an indexer) would not have the same override effect.
Complicated, but very useful.
Complicated, but very useful.
I’m hopeful
1
person likes this idea
I like this idea!
Tell me when this idea gets some attention.
The more people who like this idea, the more it gets noticed.
The more people who like this idea, the more it gets noticed.
Create a customer community for your own organization
Plans starting at $19/month
-
Inappropriate?A further thought on this is if a high CPU cycle process starts (say over 50%) while I'm not idle and then I go idle, the idle should be ignored because obviously my computer is so busy that I'm just waiting for it to complete the process before I can continue my work. Once the process finishes, if I remain idle, then logging would stop.
I’m still hopeful
-
Inappropriate?From a personal performance perspective that sounds like cheating...
From a billing perspective I can understand where the idea comes from
