Welcome to MilkyWay@home

Posts by Adi

1) Message boards : Number crunching : Broken WUs (Message 31876)
Posted 2 Oct 2009 by Adi
Post:
Problem solved after resetting the project.

Thanks everybody for help.
2) Message boards : Number crunching : Broken WUs (Message 31638)
Posted 27 Sep 2009 by Adi
Post:
Problem persists :(

Right now a task finished in 00:49:57 (as reported by boinc 6.6.40,
and close to the average for the other tasks, 00:50:17),
which is 2997 seconds of computation, but on the milkyway site it says

115351319 	112943238  	26 Sep 2009 17:31:40 UTC  	27 Sep 2009 19:18:15 UTC  	Completed, marked as invalid  	561.56  	3.23  	0.00


I'll probably reset, even detach/reattach, in the next days.
(all the other projectys are fine, and seti also runs the optimized app.).

(The errors are from trying SSE4.2, but proc only 4.1).
3) Message boards : Number crunching : Broken WUs (Message 31575)
Posted 26 Sep 2009 by Adi
Post:
No reboot (it's not winblow$), no kernel problem (some good results were done with the same kernel).

I suspect boinc client, because, with 6.6.36, i get:

Sat 26 Sep 2009 08:16:35 PM EEST	Milkyway@home	Message from server: (won't finish in time) BOINC runs 98.5% of time, computation enabled 100.0% of that


And I know this is not true, it's a problem in 6.6.36 with the boinc's scheduler.
6.4.5 and 6.6.40 get wu's, but shows only 1/8 of the time run for milky WUs (maybe because of the 8 processors?).

Well, I'll leave it as it is, waiting for a new boinc client and/or MW app.
I'll get from time to time some WUs, for testing.

Thanks again for replies, have a nice weekend.



LATER EDIT:

Supposition 1:
It seems the sequence: 6.4.5, overwritten with 6.6.36, overwritten with 6.6.40, solved the problem,
Supposition 2:
Maybe drowning the milky's queue done the trick.


I'll post to confirm/infirm that it's working, but, of course, even if it'll work, I won't know which supposition is correct :)
4) Message boards : Number crunching : Broken WUs (Message 31532)
Posted 25 Sep 2009 by Adi
Post:
Thanks for reply.

It's a server (Fujitsu-Siemens), cannot change any parameters of the procs, RAM, etc., coolers are clean (in double exemplary, to hot-plug them, also are the power sources), temps of proc/RAM/system are OK.

All the other projects are OK (seti, climate, einstein, aqua).

So the problems are definitely not the computer or boinc client.

And the milky WUs you saw were completed in around 45 mins, but are reported in ~10 min.

Right now on milky I have "No new tasks", and 0 tasks to do.
I'll try next days to get few tasks and see how are reported.
5) Message boards : Number crunching : Broken WUs (Message 31515)
Posted 25 Sep 2009 by Adi
Post:
Please look here:

http://milkyway.cs.rpi.edu/milkyway/results.php?hostid=58901

all are "Completed, marked as invalid"
except a few (3-4) I manually aborted

I even changed the boinc ver (6.4.5 and 6.6.40).

The comp is a dual quad, CANNOT be overclocked, and I didn't have this issues until now.

Thanks




©2024 Astroinformatics Group