News:

Follow BoincTasks on Twitter Facebook        Visit our website here.
BoincTasks cloud login is working again

Main Menu

Recent posts

#71
Questions / BoincTasks JS beta 2.1 release...
Last post by Aurum - September 20, 2023, 11:25:22 AM
1. With "Show CPU tasks" unchecked any WUs that display something, e.g. 3 CPUs, in the "Use" column are still displayed.
2. On the Projects tab highlighting a range executes the command for maybe the top 2 row, 1 row or none. Previous release worked fine.
3. Occasionally WUs marked "At checkpoint" keep running and the verbose label in Status column "| Checkpoint ⏸ Don't close or leave window" is removed.
4. Adjusting column widths is difficult.
5. No way to remove highlighting on all rows with at least one row remaining highlighted.
6. Reinstating right-click functions would be convenient.
#72
Beta Testing / Can not abort tasks 1.93
Last post by Ytterbium - September 19, 2023, 05:41:57 PM
If I try to abort a whole bunch of task it doesn't seem to work any sugestions where to look.
#73
Beta Testing / Re: CPU% wrong for fractional ...
Last post by hucker - September 18, 2023, 01:19:39 PM
Yes I try to make it exactly 100% busy.  But when LHC tasks are idling waiting for downloads, I might aswell have it switching in other ones.

On this main machine I use for the web etc, I tell it 1.6 CPUs each, as running VB tasks slows the interface.
#74
Beta Testing / Re: CPU% wrong for fractional ...
Last post by fred - September 18, 2023, 12:27:57 PM
Quote from: hucker on September 14, 2023, 11:00:48 PMI'd assumed the task itself reported a time, and Boinc or Boinctasks divided the processing time by the wall time.  So you're saying Boinc or Boinctasks receives a % from the OS (like you see in task manager), and uses that along with the time the task has run for, to calculate the processing time?  Something somewhere (not in the OS) must be then dividing by the number of cores in avg_ncpus, but it's using an integer and assumed nobody would ever set fractional cores.  Under 1 core is odd I admit, but it's feasible to set say 6.5 cores in an 8 core task which uses an average below what it's capable of.
I think tasks are assigned to any CPU not a fixed one and may even transfer to another CPU.
A 24 core machine can and will run way more than 27 tasks.....
But the more tasks you run the more the CPU has to switch between tasks making things less efficient.
#75
Questions / Re: BoincTasks JS beta 2.0 rel...
Last post by fred - September 18, 2023, 12:19:55 PM
2.1 should resolve most problems.
The header width adjust is still open. https://github.com/efmer/boinctasks-js/issues
Tip: To adjust the header, make all other rows smaller.
#76
Beta Testing / Re: CPU% wrong for fractional ...
Last post by hucker - September 14, 2023, 11:00:48 PM
I've just experimented by changing <avg_ncpus> on the fly.  It's rounding it up to the next whole number.  1, 2, 3, 4, 5, 6 all work fine.  0.8 gives the same percentage as 1.  1.1 gives the same percentage as 2.

However it does work for scheduling.  If I change 1 to 0.9 on a 24 core machine, it runs 27 tasks instead of 24.

I'd assumed the task itself reported a time, and Boinc or Boinctasks divided the processing time by the wall time.  So you're saying Boinc or Boinctasks receives a % from the OS (like you see in task manager), and uses that along with the time the task has run for, to calculate the processing time?  Something somewhere (not in the OS) must be then dividing by the number of cores in avg_ncpus, but it's using an integer and assumed nobody would ever set fractional cores.  Under 1 core is odd I admit, but it's feasible to set say 6.5 cores in an 8 core task which uses an average below what it's capable of.
#77
Beta Testing / Re: CPU% wrong for fractional ...
Last post by fred - September 14, 2023, 12:55:52 PM
I wonder if <avg_ncpus>0.7</avg_ncpus> does anything besides showing on the screen.
BoincTasks shows the actual run % reported by the OS to the Boinc Client -> BoincTasks.
70 min out of 100 min = 70% 100 min out of 100 min = 100%.
0.7 = expected run time 70%.
#78
Beta Testing / Re: CPU% wrong for fractional ...
Last post by hucker - September 14, 2023, 07:34:16 AM
The 0.7C was me using an app_config:

    <app_version>
        <app_name>Theory</app_name>
        <plan_class>vbox64_theory</plan_class>
        <avg_ncpus>0.7</avg_ncpus>
    </app_version>

This may seem an odd thing to do, but Theory on LHC downloads massive amounts of data, an d often the CPU is held up waiting, so I run more tasks than I have CPU threads.

If I have set 0.7C, and the times are showing say 70min out of 100min, that ought to show as 100%.
#79
Beta Testing / Re: CPU% wrong for fractional ...
Last post by fred - September 14, 2023, 06:14:04 AM
The CPU calculates these numbers. 0.7C is just an estimate and the real fraction may be something else.
#80
Beta Testing / Re: CPU% wrong for fractional ...
Last post by hucker - September 13, 2023, 08:00:14 PM
But which program calculates the % from those numbers?  I can have 03:15:45 (02:46:40) 85.14% 0.7C, where the 0.7 is not taken into account.  Things like 6C are ok though.