What is your CPU to Run time difference?
Have you gone through your stderr file to see if anything abnormal showed up there?
An idea what percentage of the core that task is using?
30 hours is absurd. If it doesn't finish in 8 CPU time, then it stuck somehow.

Update, I made a mistake.

I actually only have 2 machines (of 7) that can run Rosetta Python. VB 5 makes Cosmology work. Antivirus settings make LHC work. But Rosetta needs a CPU with AVX (or maybe FMA) instructions, and 5 of mine are too old.

So I got 3 aaam tasks, one on an i5-8600K which works ok. Two on a Ryzen 9 3900XT, which both work ok.

From what i could understand his tasks do not fail, but some run for 30 hours before completing.

That is a fail. If they run 30 hours, it means no calculations are actually being done. I assume something times out.

Boinctasks is helpful to show any tasks where the CPU usage had dropped to near 0. I find this happens on some machines more than others but I'm not sure why. Windows seems more problematic than Linux.

Typically, I find that VirtualBox tasks that have run for more than 10hrs are broken and need aborting. Unfortunately, that often also triggers the project to stop you getting more VB tasks until you click the Allow button again.

---

Subject: +30 hours to run 8 hr tasks

I recently installed VB. I'm on Win 11, Intel i5-11, running VB 6.1.32 (the recommended Boinc version), and all Rosetta tasks are estimated by Boinc to take 8 hrs, which sometimes take 4 hrs, and some take +30 hrs. Is this normal? The ones that take the longest often indicate, for ex, time remaining = 30 min, and 8 hrs later, the time remaining = 20 min -- which seems odd. Do I need to tweak something?

It can take some days for Boinc to get used to your system and how quickly it runs. To help it do so make sure you run the benchmarks.

Having said that, Rosetta is different to other projects in that it has fixed length jobs rather than jobs with a fixed amount of work. There are two things that can interfere with that, firstly if the task has a low number of starting points you might run for a shorter time than selected, often 3 hours rather than 8, and secondly if the task takes more than the selected time to run the first iteration of the work as it only checks whether to finish at the end of each iteration.

Ach! I forgot Python and it’s failings - yes, this is likely to be vb going to sleep and only pretending to work.

My last two tasks took 3 hours and 8 minutes and 3 hours and 22 minutes on my Windows 11 Intel i5 and Virtual Box 6.1.32.RAM is 12 GB.
Tullio

---

I have got connection reset errors several times while sending reply.

Subject: +30 hours to run 8 hr tasks

I recently installed VB. I'm on Win 11, Intel i5-11, running VB 6.1.32 (the recommended Boinc version), and all Rosetta tasks are estimated by Boinc to take 8 hrs, which sometimes take 4 hrs, and some take +30 hrs. Is this normal? The ones that take the longest often indicate, for ex, time remaining = 30 min, and 8 hrs later, the time remaining = 20 min -- which seems odd. Do I need to tweak something?

It can take some days for Boinc to get used to your system and how quickly it runs. To help it do so make sure you run the benchmarks.

Having said that, Rosetta is different to other projects in that it has fixed length jobs rather than jobs with a fixed amount of work. There are two things that can interfere with that, firstly if the task has a low number of starting points you might run for a shorter time than selected, often 3 hours rather than 8, and secondly if the task takes more than the selected time to run the first iteration of the work as it only checks whether to finish at the end of each iteration.

Ach! I forgot Python and it’s failings - yes, this is likely to be vb going to sleep and only pretending to work.

Look through you stderr file and see if you can find anything unusual. Lost comm or something that burped weird during the process. Look for radical time change message. Compare your CPU run time vs actual run time where it makes checkpoints. If they are not close then something went wrong prior to where the values become to far apart to make any sense. See if you can find anything in the text.
If you can't then it is something BOINC can not identify and you can write it up to a "bug" from the person who wrote that protein sequence.

Repeating my earlier message for those who haven't seen it:

If you have a task you think is stalled or taking a long time, click on it and select properties on the left.
If there's a large difference between CPU time and Elapsed time, then it's stalled and you can only abort it. They <never> restart.

Also, if later tasks are completing before earlier tasks, it's a clue to check Properties of those earlier tasks and, if they've stalled in the way described above, abort them.
This wastes the least amount of processing time.

It's not your fault and there's <nothing> you can do to correct it

---

Cosmology doesn't need it. I can run Cosmology on all 7 of my machines, most are missing AVX. The only thing that annoys Cosmology is VB 6. VB 5 is ok.

Had a look , the q9450 is on Boinc 7.16.20 so its got VB 6.1.2
I will finish all work and revert/uninstall/nuke back to Boinc 7.14.2 uses VB 5.2.8 to see what happens .
I have got versions of boinc mangler back to 5.10.13
Oh! , that's 45 all together in win/Lin 32/64/VB or not , sad case . . . .
Just in case .
But sometimes they come in usefull .

I stick with the latest Boinc (well actually later than latest because I have contacts) but just change the VB version.

Cosmology doesn't need it. I can run Cosmology on all 7 of my machines, most are missing AVX. The only thing that annoys Cosmology is VB 6. VB 5 is ok.

Had a look , the q9450 is on Boinc 7.16.20 so its got VB 6.1.2
I will finish all work and revert/uninstall/nuke back to Boinc 7.14.2 uses VB 5.2.8 to see what happens .
I have got versions of boinc mangler back to 5.10.13
Oh! , that's 45 all together in win/Lin 32/64/VB or not , sad case . . . .
Just in case .
But sometimes they come in usefull .

I stick with the latest Boinc (well actually later than latest because I have contacts) but just change the VB version.

Reverting did no good , it still won`t run any VB tasks from Rosetta or Cosmo , it trashes them
so put it back to 7.16.20 without VB Looks like a Q9450 haznt got what it takes to run boinc `s kind of VB stuff on the projects that I do .
And I will not be bothering to try out others to see what happens .

Over at Cosmo my opteron16 system does work with 7.16.20 and VB 6.1.2 with little or no bother

Cosmology doesn't need it. I can run Cosmology on all 7 of my machines, most are missing AVX. The only thing that annoys Cosmology is VB 6. VB 5 is ok.

Had a look , the q9450 is on Boinc 7.16.20 so its got VB 6.1.2
I will finish all work and revert/uninstall/nuke back to Boinc 7.14.2 uses VB 5.2.8 to see what happens .
I have got versions of boinc mangler back to 5.10.13
Oh! , that's 45 all together in win/Lin 32/64/VB or not , sad case . . . .
Just in case .
But sometimes they come in usefull .

I stick with the latest Boinc (well actually later than latest because I have contacts) but just change the VB version.

Reverting did no good , it still won`t run any VB tasks from Rosetta or Cosmo , it trashes them
so put it back to 7.16.20 without VB Looks like a Q9450 haznt got what it takes to run boinc `s kind of VB stuff on the projects that I do .
And I will not be bothering to try out others to see what happens .

Cosmology should run on anything if you use VB 5. Look at these old things I'm using on it:

https://boinc.bakerlab.org/rosetta/show_host_detail.php?hostid=6181958
https://boinc.bakerlab.org/rosetta/show_host_detail.php?hostid=6181968

The second one uses DDR2 RAM! Both run Cosmology perfectly. Your computers are better than those, even your Core 2 Quads are newer than mine.

Looks like I waz editing my above post while you where replying to it
I see they are both on win 11 , I wonder if that haz anything to do with it , as the Q9450 iz still on wind7 .
Though the opteron iz on wyn 7 and crunch`s along without any bother , such iz life .

Q9450 Doesn't support AVX. Virtualbox jobs get stuck if avx is missing.

Looks like I waz editing my above post while you where replying to it
I see they are both on win 11 , I wonder if that haz anything to do with it , as the Q9450 iz still on wind7 .
Though the opteron iz on wyn 7 and crunch`s along without any bother , such iz life .

I don't think I was doing cosmology back on windows 10. It is possible that 11 helps, I think the way the OS uses the CPU is different. Just get 11 onto them, use "Rufus" - it can bypass the TPM requirement, I used an 8GB USB stick to perform an upgrade. You can probably do it just on the hard disk if you don't have one.

Q9450 Doesn't support AVX. Virtualbox jobs get stuck if avx is missing.

Not on cosmology or LHC, that's only a Rosetta requirement. I have 5 computers with no AVX and they all run Cosmology and LHC VB tasks fine.

Selecting 2 Hours seams to really take up to and even more than a day.
I can this be fixed?

Selecting 2 Hours seams to really take up to and even more than a day.
I can this be fixed?

Each task is divided into sections called decoys. The checks of whether to end a task are normally only run at the end of a decoy, except for a check that the task has run so long that its outputs are unlikely to be very useful.

For the Rosetta tasks, this is probably unfixable. It usually means that the time per decoy for this task is much more than two hours, and you're unlikely to accomplish anything before the first decoy finishes.

For the Python tasks, you can partially fix some of them by comparing the emulated CPU time with the CPU time used by the emulation, and aborting them if they start using much more CPU time for running the emulation than the emulated CPU time, expect for a few minutes for starting up the emulation.

BOINC is giving me error messages about being unable to run Python tasks because the need very large amounts of free memory to even start, such as about 19 GB. Is this a real requirement for them, or just bad calculations?

BOINC is giving me error messages about being unable to run Python tasks because the need very large amounts of free memory to even start, such as about 19 GB. Is this a real requirement for them, or just bad calculations?

Sometimes they ask for more than they will actually need, but they do use a lot. For example I have a 6 core i5 with 16GB of RAM. It can get 5 Pythons running, then the memory is 80-90% full and doesn't load the 6th.

19GB sounds unusual, since that would stop any from running on my above machine at all, and I've never seen that.