Recent posts

#61

Wish List / Re: Can't abort many tasks.

Last post by fred - December 26, 2025, 08:10:13 AM

By "very dangerous" I assume you mean users lose work by mistake?

Right, this isn't something to do every day.

#62

Wish List / Re: Incorrect core usage displ...

Last post by fred - December 26, 2025, 08:09:31 AM

Isn't this a BOINC client thing, maybe the cpu usage can't go any lower than that.

#63

Wish List / Incorrect core usage displayed

Last post by hucker - December 25, 2025, 08:35:11 PM

    <app>
        <name>ap26</name>
        <max_concurrent>0</max_concurrent>
        <gpu_versions>
            <gpu_usage>0.330000</gpu_usage>
            <cpu_usage>0.001000</cpu_usage>
        </gpu_versions>
        <fraction_done_exact>1</fraction_done_exact>
        <report_results_immediately>0</report_results_immediately>
    </app>

Results in:

#64

Wish List / Re: Can't abort many tasks.

Last post by hucker - December 25, 2025, 08:10:45 PM

By "very dangerous" I assume you mean users lose work by mistake?

#65

Wish List / Re: Can't save colours

Last post by hucker - December 25, 2025, 08:09:34 PM

Sorry to waste your time, I should have mentioned dark mode!

I take it 2.7 is in the works as my 2.6.2 says up to date.

#66

Wish List / Re: Can't abort many tasks.

Last post by fred - December 25, 2025, 12:52:45 PM

It's more or less by design, since deleting all tasks in a filter is very dangerous.
Open the filter and select the tasks.
It's a bit more work, but much safer.

#67

Wish List / Re: Can't save colours

Last post by fred - December 25, 2025, 12:50:20 PM

Interesting it took me a couple of hours to find the cause.

https://github.com/efmer/boinctasks-js/issues/141

#68

Wish List / Can't save colours

Last post by hucker - December 25, 2025, 12:55:50 AM

The ok button is damn hard to see!

#69

Wish List / Re: BoincTasks JS CPU% calcula...

Last post by fred - December 24, 2025, 08:50:23 AM

In BoincTasks Clasic The calculation is the same, but removing the check at CPU % Long time average.
The interval is much shorter.

What I will do is add and optional calculate the delta between two reads.
That way you see an immediate result

What I added >>>  Readings between two intervals.

       >>>         cpuTime = cpuTime - cpuTimeOld;
       >>>         elapsedTime = elapsedTime - elapsedTimeOld;

                let cpu = 0;
                if (cpuTime == 0 || elapsedTime == 0)
                {
                    resultItem.cpu = 0;
                }   
                else
                {             
                    cpu = (cpuTime/elapsedTime) * 100;
                    if (cpu > 100) cpu = 100;
                    resultItem.cpu = cpu;                 
                }

Old is the previous reading;

#70

Wish List / BoincTasks JS CPU% calculation...

Last post by hucker - December 24, 2025, 02:04:39 AM

Hi Fred,
�I've noticed a difference in how BoincTasks JS calculates the CPU % column compared to the original desktop BoincTasks.
�In the original BoincTasks, the CPU % was calculated as (CPU Time / Wall Time). If I had an LHC Theory task assigned to 3 CPUs but it only utilized ~1.1 cores (as verified in Windows Task Manager), it would correctly show about 33-38%. 
�However, in BoincTasks JS, the column shows 100% regardless of actual internal VM utilization, as if it is reporting "Slot Reservation" rather than "Actual CPU Time Efficiency." Non-VM tasks (like MilkyWay) still seem to report correctly (~98%).
�Could you consider bringing back the (CPU Time / Wall Time) calculation for the CPU % column in the JS version? It helps me identify when a VM is being "sluggish" or under-utilizing its allocated cores, which is very helpful for system utilisation.
�Thanks for all your work on the JS version!