Posts by [AF>Le_Pommier] Jerome_C2005
|
1)
Message boards :
Number crunching :
When will you update yafu to version 2?
(Message 1698)
Posted 3 Jan 2023 by [AF>Le_Pommier] Jerome_C2005 Post: Maybe the fault of gfns but then why don't implement a control mechanism to detect when it is clearly stuck : for example we can see the log files not being updated anymore in the slot directory, we can see only one gfns process running endlessly and all the other threads idle... So define a "security time" after which task to be stopped if such conditions are met - with error code and loss of credits, or not, this is another debate. Happy new year ;) |
|
2)
Message boards :
Number crunching :
No more tasks (< 16t) ?
(Message 1651)
Posted 26 Sep 2022 by [AF>Le_Pommier] Jerome_C2005 Post: Yes I had posted because at some point there were none, but now it went back to usual behavior : 1 task running / 2 tasks ready to start. Cool :) |
|
3)
Message boards :
Number crunching :
No more tasks (< 16t) ?
(Message 1648)
Posted 18 Sep 2022 by [AF>Le_Pommier] Jerome_C2005 Post: Thanks, tasks are back ! In very limited amounts, but there are some. |
|
4)
Message boards :
Number crunching :
No more tasks (< 16t) ?
(Message 1646)
Posted 16 Sep 2022 by [AF>Le_Pommier] Jerome_C2005 Post: Hello it seems there are only 16t and 32t tasks left... is this temporary ? Thx |
|
5)
Message boards :
Number crunching :
Wrong Core Parameter on 8t WUs?
(Message 1628)
Posted 10 Jun 2022 by [AF>Le_Pommier] Jerome_C2005 Post: Oh OK, so it changed then : I think that before I could have 2 parallel 4t tasks running on my i5 / 8 threads. Good to know this is normal :) |
|
6)
Message boards :
Number crunching :
Wrong Core Parameter on 8t WUs?
(Message 1626)
Posted 9 Jun 2022 by [AF>Le_Pommier] Jerome_C2005 Post: I confirm that now they are not limited to 1 thread, however now the behavior of the 4t task is the opposite : they are actually using 8 threads !   WTH ? |
|
7)
Message boards :
Number crunching :
Wrong Core Parameter on 8t WUs?
(Message 1625)
Posted 7 Jun 2022 by [AF>Le_Pommier] Jerome_C2005 Post: The first task did terminated and got (modestly) credited after more than 4 days of calculation. The second one (4t task) is still running (and has some "extra deadline" to finish yet) but suddenly at some point it decided it should run on 8 available threads (it is a 4t !!!) --> I see 8 gnfs-lasieve process now running in memory And I know these processes do correspond to *this* running task because - the slot contains work files dated 01/06, 02/06... and in the log files I see references from 01/06 onwards - the other 2 tasks sent to me on 5 and 6 June are still pending to run and have 0 crunch time (and not even a slot directory assigned). Strange isn't it ? |
|
8)
Message boards :
Number crunching :
Wrong Core Parameter on 8t WUs?
(Message 1622)
Posted 5 Jun 2022 by [AF>Le_Pommier] Jerome_C2005 Post: Oh you are right I had not noticed the difference of deadline on my project account, what is June 1st and 3rd on my boinc manager is 11th and 13th here. However for both task the only file being updated from time to time is stderr.txt (4 hours ago for both) where it adds one "total yield" row, the 2 logs files have not been updated since yesterday morning (my previous screenshot is still valid for these). I really wonder if it's of any use to let these run, I'd like to see yoyo's opinion on this. |
|
9)
Message boards :
Number crunching :
Wrong Core Parameter on 8t WUs?
(Message 1620)
Posted 4 Jun 2022 by [AF>Le_Pommier] Jerome_C2005 Post: Now the update ratio of the log files seems to be quite low, but still it looks like it is still doing something... only the stderr.txt seems to be updated more often, for both tasks 04/06/2022 07:52 - factor.log 04/06/2022 07:52 - ggnfs.log 31/05/2022 21:21 - session.log 04/06/2022 16:50 - stderr.txt 04/06/2022 07:52 - wrapper_checkpoint.txt 04/06/2022 06:55 - factor.log 04/06/2022 06:55 - ggnfs.log 02/06/2022 09:27 - session.log 04/06/2022 16:50 - stderr.txt 04/06/2022 06:55 - wrapper_checkpoint.txt and with deadlines that were on 01/06 and 03/06 will they still be considered if they ever return a result ? |
|
10)
Message boards :
Number crunching :
Wrong Core Parameter on 8t WUs?
(Message 1618)
Posted 4 Jun 2022 by [AF>Le_Pommier] Jerome_C2005 Post: The main question was more "how long shall I let them run" then the "too many" problem, especially if you consider each one was only running 1 thread. Now the 3rd one has terminated after 2 days 7 hours, but the other are still running with 81 and 46 hours of run... It seems the continue to update the log but with less frequency : more than 4 hours ago for both. Also now there is another YAFU v134.05 (mt) fully running (all thread) at the same time... So shall I try to let the 2 remaining 4t terminate ? |
|
11)
Message boards :
Number crunching :
Wrong Core Parameter on 8t WUs?
(Message 1616)
Posted 3 Jun 2022 by [AF>Le_Pommier] Jerome_C2005 Post: Since more than a week I have system issue with never ending tasks  since last week I have canceled other tasks with the same issue, this is running on a i5 8t (so how on earth could it decide to calculate 3 4t tasks ?), they all have *one* gnfs-lasieve (really) running during some time (more than 1 hour) then restarting another one, and loging rows into factor.log, ggnfs.log and (sometimes) stderr.txt so "it looks like they are not really dead" (I had some dead tasks in the past when nothing was written in any log for hours) but now I really don't know what do it, this is now reccurrent (I have canceled similar ones and others are behaving the same over and over). |
|
12)
Message boards :
Number crunching :
Strange deadline management
(Message 1456)
Posted 11 Nov 2019 by [AF>Le_Pommier] Jerome_C2005 Post: Hi I have a task that ran for more than a day that then got suspended by another task because its deadline is shorter and boinc decided that the 2nd one needs to run in priority :  Is this normal ? There is no risk that the suspended task gets rejected by the server if the new one runs for too long ? Thanks |
|
13)
Message boards :
Number crunching :
Stuck at 100% for nearly 6 days !!
(Message 1134)
Posted 21 Feb 2018 by [AF>Le_Pommier] Jerome_C2005 Post: This one apparently crashed after more than one day of crunching : I think the computer rebooted because of forced upgrade on the machine (corporate policy, if you are not in front of the machine you have no action to prevent it...) but the checkpoint mechanism of yafu didn't work then ? It's a pity... |
|
14)
Message boards :
Number crunching :
Error: Can't link app version file
(Message 1129)
Posted 19 Feb 2018 by [AF>Le_Pommier] Jerome_C2005 Post: Most of the antiviruses allow to exclude some folders from scanning in their settings, to avoid reporting false positive (and blocking apps, like boinc) --> add boinc data folder in there. Boinc apps never include malware or virus, ask Berkeley why - or better read the well documented wiki pages regarding boinc security of applications. |
|
15)
Message boards :
Number crunching :
Stuck at 100% for nearly 6 days !!
(Message 1128)
Posted 19 Feb 2018 by [AF>Le_Pommier] Jerome_C2005 Post: At my side I have this task that started to crunch on 16/02/2018 11:13:03, I think it has been "100%" since 2 days, it's still running and "doing stuff" (see logs updating in the slot, progs crunching in memory) ... 19/02/2018 16:49:45 v1.34.5 @ FRHD-L509624, nfs: commencing lattice sieving with 4 threads 19/02/2018 17:28:18 v1.34.5 @ FRHD-L509624, nfs: commencing lattice sieving with 4 threads deadline was yesterday morning. I let it crunch since I can see it's doing stuff, but I report it because you mentioned it was useful. |
|
16)
Message boards :
Number crunching :
Diffrence between app "YAFU 134.05 (mt)" and app "YAFU-4t 134.05 (4t)"
(Message 1125)
Posted 17 Feb 2018 by [AF>Le_Pommier] Jerome_C2005 Post: Thanks for the (quick and clear) answer. |
|
17)
Message boards :
Number crunching :
Diffrence between app "YAFU 134.05 (mt)" and app "YAFU-4t 134.05 (4t)"
(Message 1120)
Posted 15 Feb 2018 by [AF>Le_Pommier] Jerome_C2005 Post: Hi it may have been answered here but I couldn't find it, what is exactly the difference between app "YAFU 134.05 (mt)" and app "YAFU-4t 134.05 (4t)" ? I get both of them on my i5 and the WU names are very similar, and I can't find a difference the way they are running : all the core are used, there are phases with 4 threads (ECM or <something else>) and phases where yafu.exe is running 4 cores, or only 1... (or maybe I didn't look close enough and I got confused ?) Thanks |
|
18)
Message boards :
Number crunching :
Slower and slower, then sticks at 100%
(Message 1109)
Posted 10 Feb 2018 by [AF>Le_Pommier] Jerome_C2005 Post: It is very difficult to participate when you use a windows machine where boinc cannot access internet most of the time (I use a USB key once a week to move WUs to a connected win VM in my Mac). I've had the machine exceptionally at home for a few days (thanks to the snow in Paris :) ) so I could let it run connected to the net (out of corporate network) so I decided to give another try with yafu, I got a very short WU first (3 secs of run only !) and then I have one of those long ones that already reached 100% and is running, I can see the logs are updating in the slot, apps running in memory so I know "it's OK" but what worries me is that if it doesn't finish by Monday morning (and the deadline is tomorrow afternoon), that machine will go back to the office with no connection for boinc. Supposing the WU then finishes during the week it won't be sent back before the next week-end so who knows if it will still be considered valid and accepted by yafu... |
|
19)
Message boards :
Number crunching :
Slower and slower, then sticks at 100%
(Message 1093)
Posted 17 Dec 2017 by [AF>Le_Pommier] Jerome_C2005 Post: I have this WU running for less than 10mn and with less than a minute of reported CPU time, and then this one running for almost 3 days that I finally canceled : I had to suspend it / stop the computer, when I restarted it had lost all the running time and went back to 16 hours, and then I let it run for almost 2 days before I canceled it and now it says 1d18 hours running and less than 16 hours of CPU credited... this is all nonsense and very poorly managed : the cruncher needs a precise information on run time estimate and deadline, it is not boinc that "invents" runtime but the application that provides information to boinc about it's internals, we don't want some WU "working the time they want" and "deadlines that mean nothing don't worry". Crunchers deserve a little more respect than this, I'm giving my CPU power and I pay the energy to run it, I don't like to be treated as an ignorant kid and "you don't need to understand that" kind of behavior. |
|
20)
Message boards :
Number crunching :
0% WU...
(Message 964)
Posted 24 Mar 2017 by [AF>Le_Pommier] Jerome_C2005 Post: Mmmmm... it terminated around midnight, after more than 30 hours of calculation... the 2nd I had in queue then started... and terminated after less than 30mn !!! 23-Mar-2017 23:54:16 [yafu] Computation for task yafu_ali_502776_L134_C126_1490169005_285_0 finished What the hell with this project, on the computer I'm trying to run Yafu, Boinc cannot access internet (proxy restrictions), I move WU manually via USB key from my home computer, next contact with Internet will be tonight, so I don't even know if those 2 WUs will be validated (both had deadline this morning 9am)... |
Next 20
Datenschutz / Privacy Copyright © 2011-2024 Rechenkraft.net e.V. & yoyo