Hello evryone, best wishes for new year.
Strange, some WU runs in a few seconds,
But some runs about 30 minuts, then start again from null ! with remaining of some hours !
And those WU, starts again and again !!!
The worst is that such WU (running hours) are considered/reported as working time in a few seconds !
What is the problem ?
My side ?
Best regards

---

Hello evryone, best wishes for new year.
Strange, some WU runs in a few seconds,
But some runs about 30 minuts, then start again from null ! with remaining of some hours !
And those WU, starts again and again !!!
The worst is that such WU (running hours) are considered/reported as working time in a few seconds !
What is the problem ?
My side ?
Best regards

Hello! :)

Most of tasks are short and runs ~ 10 .. 20 seconds. But some tasks (about 1/10 .. 1/20 part of entire set) - long and must runs 1, 2, 3, may be more hours (depending of computer). During computation of this tasks BOINC periodically performs update of estimation run time and percent of completion. And tasks does not have checkpoints.

Thank you for participation!

Hello Hoarfrost,
I know you do your best. Already many years.
We know each other also many years.
But the strange running time is very special.
Some WU runs 1 or 2 hours, Then restart again and again.
With the latest running in some second. With result that credits are very low.
When a WU is estimated remaining is above the 3 hour, I cancel.
Some WU have a remaining above the five hours !!!
The problems is that the stderr.txt, stay empty !
What I do ????????????
Best regards

---

Hello! :) Would you post links to strange tasks or its names or other info? I will try to investigate this. It's very strange.

Thank you for information!

Hello Hoar
Look https://rake.boincfast.ru/rakesearch/results.php?hostid=3396&offset=0&show_names=0&state=6&appid=
All WU are anounced to run in a few second (less than one minut)
After more than one hour running, "remaining time" increase to 2 , 3 or 4 hours !!!
Worst : wu_e1056_n12_ddlx_sq12_wu0709064_t1613_3354-3413
Look remaining time : seven hours !!!!!!!!!!!!!
I will not cancel this one, .
Best regards

Application
Joint search of ODLS12 with Gerasim project 1.00
Nom
wu_e1056_n12_ddlx_sq12_wu0709064_t1613_3354-3413
État
Calculs en cours
Reçu
1/04/2022 14:23:18
Date limite d'envoi
8/04/2022 14:23:10
Taille de tâche estimée
1.000.000 GFLOPs
Temps de calcul
00:36:52
Temps processeur depuis le point de sauvegarde
00:36:52
Temps écoulé
00:38:43
Temps restant estimé
07:13:11
Portion effectuée
8,201%
Taille de la mémoire virtuelle
140,20 MB
Espace mémoire alloué
117,88 MB
Répertoire
slots/11
ID du process
12308
Taux de progression
14,040% par heure
Exécutable
rake_odls12_wrapper_windows_intelx86_64.ex

.

Hello! :) Would you post links to strange tasks or its names or other info? I will try to investigate this. It's very strange.

Thank you for information!

Hello Hoarfrost, again a strange WU :
I write on apr01 17:40UTC
It run in one minut till 99% then restart again from null. Now 4 hours remaining, and time uncreasing. After waiting one hour , it show now six hours !!!
My hosts runs 24/7/365.
It is the same on my two hosts. Some runs normal, some fully unexpected,

About this WU,
Here the stderr.txt :
19:04:44 (7452): wrapper (7.9.26016): starting
19:04:44 (7452): wrapper: running rake_odls12_windows_intelx86_64.exe ()
Error: startup_info.hStdInput is invalid

Fraction done.txt:
3.72238358715549E-0001

All those report are from 17:04 UTC (the hour you read are in my local time !)

Best regards.





Application
Joint search of ODLS12 with Gerasim project 1.00
Nom
wu_e1056_n12_ddlx_sq12_wu0712041_t1620_3061-3120
État
Calculs en cours
Reçu
1/04/2022 16:39:55
Date limite d'envoi
8/04/2022 16:39:47
Taille de tâche estimée
1.000.000 GFLOPs
Temps de calcul
00:12:49
Temps processeur depuis le point de sauvegarde
00:12:49
Temps écoulé
00:12:17
Temps restant estimé
06:18:06
Portion effectuée
3,138%
Taille de la mémoire virtuelle
140,04 MB
Espace mémoire alloué
117,79 MB
Répertoire
slots/1
ID du process
12356
Taux de progression
23,040% par heure
Exécutable
rake_odls12_wrapper_windows_intelx86_64.ex

very strange !!!
Now a WU predicted for years !!!
Application
Joint search of ODLS12 with Gerasim project 1.00
Nom
wu_e1056_n12_ddlx_sq12_wu0715879_t1629_3310-3369
État
Calculs en cours
Reçu
1/04/2022 19:35:42
Date limite d'envoi
8/04/2022 19:35:34
Taille de tâche estimée
1.000.000 GFLOPs
Temps de calcul
00:05:31
Temps processeur depuis le point de sauvegarde
00:05:31
Temps écoulé
00:07:33
Temps restant estimé
-1293120d -16:-17:-12
Portion effectuée
0,000%
Taille de la mémoire virtuelle
140,02 MB
Espace mémoire alloué
117,76 MB
Répertoire
slots/7
ID du process
8952
Exécutable
rake_odls12_wrapper_windows_intelx86_64.exe

Hi!

Does the expected time change to usual values after 10 .. 15 minutes of computing?

Thank you!

Hi!

Does the expected time change to usual values after 10 .. 15 minutes of computing?

Thank you!

Hello, No,
Some WU are at 98% after 2 or 3 minutes.
Then restart with remaining in hours (sometimes 5 hours)
Some restarted WU (after 2 or 3 minutes) , after one hour stay remaining time in hours !!!
Thank you for your help. (by the way, normally you have my private mail? Remember a few years ago the problem with Natalia.
We are "friends" by private No any problem to send you much more détails.

Hello!

Estimation of runtime can varies in wide range. Only real run time have a sense. Usually between seconds and 30 .. 60 minutes for Ryzen. If you see a very long tasks you can list it to me in private project mail.

Thank you for attention! :)

Hello Hoarfrost, I will do.
Thank you for your help
Best regards

This task became stuck on 73.33%.
It stayed stuck at that point at least 16 hours. I've aborted it after giving it a try to complete.

This task became stuck on 73.33%.
It stayed stuck at that point at least 16 hours. I've aborted it after giving it a try to complete.

Thank you, V0d01ey! It looks like some kind of rare problem. The other two results were calculated correctly.