I have my computer run on 60% of processing time. The elapsed and remaining time both seem to indicate only the time the processor was actually working. So to both times I have to add another 50% or so to get the correct values. Is that just a setting problem or intended that way? I would rather see times which run continously to get a better feeling for changes to more or less processing time for example. Boinc manager version 07.16.07, Windows 10, all projects

I have my computer run on 60% of processing time. The elapsed and remaining time both seem to indicate only the time the processor was actually working. So to both times I have to add another 50% or so to get the correct values. Is that just a setting problem or intended that way? I would rather see times which run continously to get a better feeling for changes to more or less processing time for example. Boinc manager version 07.16.07, Windows 10, all projects

Consider setting %cpu to 60 instead of %time, it’s more efficient and your figures will show what you want them to.

Also consider dropping your cache size, you don’t need to hold 160 hours work for one of many projects unless your internet connection is totally unreliable :-)

Ok, how do I set the cpu to only 60% instead of cpu time? I can find only a setting for cpu time. The cache is set to 0.2 + 02. working days. The computer is thus not holding a lot of work standy by.

There are two ways of setting this value: either globally, through the website of one of the projects your computer is attached to, or locally via BOINC Manager. They can't be mixed: once you set any local value, local values take precedence and the website values are disregarded.

It sounds like you may be using local, BOINC Manager, settings. To see the alternative setting, you need to be in Advanced View, not Simple View. Switch from the View menu, or use the keyboard shortcuts: Ctrl+Shift+A for Advanced, or Ctrl+Shift+V for Simple.

I used the advanced local settings. You mean to reduce the number of cores involved in the calculation. Got ya!

I changed the setting like you said with cpu's to 70% and cpu computing time to 100% resulting in a reduction of 3 tasks to a total of 5 at the same time. Unfortunatetly the remaining cores heat up to about 80 degrees celsius which is way too hot for continous work so I had to revert to the old settings.

With this I am asking for a change in the BOINC manager to show the elapsed and remaining times counting continously irrespective of cpu times setting.The way it is at the moment it is just confusing!

I changed the setting like you said with cpu's to 70% and cpu computing time to 100% resulting in a reduction of 3 tasks to a total of 5 at the same time. Unfortunatetly the remaining cores heat up to about 80 degrees celsius which is way too hot for continous work so I had to revert to the old settings.

With this I am asking for a change in the BOINC manager to show the elapsed and remaining times counting continously irrespective of cpu times setting.The way it is at the moment it is just confusing!

Whether the remaining time drops continuously or jumps is down to the individual project’s application not the Boinc Manager. The elapsed should always count continuously.

For interest, why 70% rather than the 60% you started with? As I understand the max temp for your Ryzen is 95c, certainly my Ryzen 5s were perfectly happy at 80c running 100% cpu although I’ve now rejigged the cooling so they’re now running about 75c.

For interest, why 70% rather than the 60% you started with? As I understand the max temp for your Ryzen is 95c, certainly my Ryzen 5s were perfectly happy at 80c running 100% cpu although I’ve now rejigged the cooling so they’re now running about 75c.

I thought that while the max is 95C, boost throttling starts much lower? I would get improved cooling, especially if you have a stock cooler. It really doesn't cost very much to get something that will make a significant difference.

With this I am asking for a change in the BOINC manager to show the elapsed and remaining times counting continously irrespective of cpu times setting.The way it is at the moment it is just confusing!

Elapsed time is the actual wall-clock time. Remaining time is an estimated time, based on the amount of flops the project states the task takes but which your CPU will probably much faster run through. Hence estimated, as not all computers use the same CPU which calculate the same amount of flops per task.
These counters are only counting time when actual science is done on the CPU. So not when BOINC is paused, not when the science application is paused. Not when BOINC has exited.

By using 60% processing time, you tell BOINC to run the science applications for 6 seconds per 10 seconds at 100% and to pause it for the other 4 seconds. When the application is paused, it doesn't use CPU, so that time isn't counted. BOINC will however also count the CPU time. You can find this one in Properties of the individual tasks.

If you want the total time from task start to task finish including pauses, exits etc. you will have to use a third party application or make a notation of your local wall-clock when tasks start.

---