BOINC 6.6.31
When you open the BOINC manager and keep it open.
It consumes a lot of your cpu time, on my I7 it is 40-50% of one of the threads.
In the task manager this is hard to see because the value goes all over the place.
But when you measure it over a longer period as I did (2 seconds) you see the real value.
Even when you minimize it, the workload is the same.
You have to close it all together and than it drops to almost 0.

But when you measure it over a longer period as I did (2 seconds) you see the real value.

Typo maybe? Did you mean minutes, hours or days?
Unless you're an AI, for then 2 seconds is indeed a long time. :-)

You have to close it all together and than it drops to almost 0.

I would hope it goes away when you close it (File->Exit), as a completely closed BM should not be in memory.

Now, I have two BOINC Managers sitting in my system tray all the time. Neither takes up any CPU cycles. Then again, I do not have much work on either machine. having a lot of work on your computer will impact on BOINC Manager as it has to keep all the numbers visible updated somehow. It does this through RPCs, which happen once a second still. The last I read, the developers are looking for ways to minimize the impact this has.

---

But when you measure it over a longer period as I did (2 seconds) you see the real value.

Typo maybe? Did you mean minutes, hours or days?
Unless you're an AI, for then 2 seconds is indeed a long time. :-)

You have to close it all together and than it drops to almost 0.

I would hope it goes away when you close it (File->Exit), as a completely closed BM should not be in memory.

Now, I have two BOINC Managers sitting in my system tray all the time. Neither takes up any CPU cycles. Then again, I do not have much work on either machine. having a lot of work on your computer will impact on BOINC Manager as it has to keep all the numbers visible updated somehow. It does this through RPCs, which happen once a second still. The last I read, the developers are looking for ways to minimize the impact this has.

To clarify this, I have a program that measures the runtime over a period of 2 seconds (so every 2 seconds).
Looking at boincmgr.exe I get these values.
A lot of users keep a watch on the cuda tasks...so if they do and keep the screen open, even as minimized it consumes time.
It should be fairly easy to drop this to 0 when minimized. And when you have thousands of entries even once a second takes up a lot of time.
By closing I mean, use the [X]=windows close. In this case it means send to the tray.

A lot of users keep a watch on the cuda tasks...

Couple of things on this.

1. What do you think updates the screen for you to "keep watch on CUDA tasks"?
2. How many are they?
3. Are you sure it isn't the same thread that moves the data from disk/physical memory to the videocard its memory and back?

And then there are the other observations.
4. Even if minimized the numbers in BOINC Manager have to be updated somehow as else there's complaints that it takes a lot of time for them to 'normalize' when you maximize the screen again.
5. Close means Exit in my book. Click the X on BOINC Manager means minimize. (but that's me)

---

A lot of users keep a watch on the cuda tasks...

Couple of things on this.

1. What do you think updates the screen for you to "keep watch on CUDA tasks"?
2. How many are they?
3. Are you sure it isn't the same thread that moves the data from disk/physical memory to the videocard its memory and back?

And then there are the other observations.
4. Even if minimized the numbers in BOINC Manager have to be updated somehow as else there's complaints that it takes a lot of time for them to 'normalize' when you maximize the screen again.
5. Close means Exit in my book. Click the X on BOINC Manager means minimize. (but that's me)

1 I'm still a bit cuda afraid, it doesn't happen much anymore.. but sometimes the process just stops.
2 Not enough but had a couple of max 1000 warning a couple of days ago, so a lot.
3 It's the process boincmgr.exe and all its threads. So the time includes any threads it's running.
4 ok, but it's a lot of time wasted.
5 [x] means close, and it was used to close the programs (it sends a message close to the underlying program the [-] is for minimizing, but lately it is more and more used to just close the window and send it to the tray.
So just follow the trend is not a bad idea, I'm guilty as well.

Just something I found useful if you are trying to measure the total CPU time used by a process on Windows -- try Process Explorer -- it's a beefed up version of Task Manager by Sysinternals (now bought by Microsoft) that is really useful in tracking issues like this. You can view usage graphs by process and get the total CPU time used by a particular process. For something like BOINC manager on a new system these days, it should only add up to a few seconds every day I suspect.

---

Just something I found useful if you are trying to measure the total CPU time used by a process on Windows -- try Process Explorer -- it's a beefed up version of Task Manager by Sysinternals (now bought by Microsoft) that is really useful in tracking issues like this. You can view usage graphs by process and get the total CPU time used by a particular process. For something like BOINC manager on a new system these days, it should only add up to a few seconds every day I suspect.

Thanks for reminding me about that one. But as programmers go, I made something myself, that uses up as little of my resources as possible. And still displays me everything I need.
As suspected "hungry" part is only there when you have a lot of WU in stock.
When you test this on a computer with "only" a dozen or so, you don't see any load. But with a couple of 1000 WU it becomes really sluggish and "hungry" even on a top of the line machine. I see a lot of communication with BOINC client messages.