PDA

View Full Version : Problema mod truXoft


Myjungle
09-04-2006, 17:19
Ciao a tutti,
ho appena installato la mod truxoft ma ho un grave problema, il tempo di elaborazione indicato è crollato, da una media di 2900 sec a 1,300 sec. Il tempo indicato però non è veritiero visto che in realtà ci mette circa 45-50 min ad elaborare una wu.

A nessuno di voi è successa una cosa simile?


i log del client sono: 09/04/2006 16.37.43||Starting BOINC client version 5.3.12.tx36 for windows_intelx86
09/04/2006 16.37.43||libcurl/7.14.0 OpenSSL/0.9.8 zlib/1.2.3
09/04/2006 16.37.43||Executing as a daemon
09/04/2006 16.37.43||Data directory: D:\Backup\boinc
09/04/2006 16.37.43|SETI@home|Found app_info.xml; using anonymous platform
09/04/2006 16.37.43||Processor: 1 AuthenticAMD AMD Athlon(tm) 64 Processor 3200+
09/04/2006 16.37.43||Memory: 511.30 MB physical, 1.22 GB virtual
09/04/2006 16.37.43||Disk: 104.50 GB total, 3.26 GB free
09/04/2006 16.37.43|rosetta@home|Computer ID: 173830; location: work; project prefs: default
09/04/2006 16.37.43|SETI@home|Computer ID: 2116527; location: home; project prefs: default
09/04/2006 16.37.43||General prefs: from SETI@home (last modified 2006-03-14 08:06:43)
09/04/2006 16.37.43||General prefs: using separate prefs for home
09/04/2006 16.37.43||Remote control not allowed
09/04/2006 16.37.43||Listening on port 31416
09/04/2006 16.37.43||truXoft add-on: calibrate_credit = all
09/04/2006 16.37.43|SETI@home|Resuming computation for result 06oc02ab.7643.20336.678406.1.84_2 using setiathome version 418
09/04/2006 16.37.43||using earliest-deadline-first scheduling because computer is overcommitted.
09/04/2006 16.40.34|SETI@home|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
09/04/2006 16.40.34|SETI@home|Reason: Requested by user
09/04/2006 16.40.34|SETI@home|(not requesting new work or reporting results)
09/04/2006 16.40.39|SETI@home|Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi succeeded
09/04/2006 17.07.30||Rescheduling CPU: application exited
09/04/2006 17.07.30|SETI@home|Computation for result 06oc02ab.7643.20336.678406.1.84_2 finished
09/04/2006 17.07.30|SETI@home|Starting result 04oc02ab.9208.3170.579808.1.63_1 using setiathome version 418
09/04/2006 17.07.32|SETI@home|Started upload of 06oc02ab.7643.20336.678406.1.84_2_0
09/04/2006 17.07.35|SETI@home|Finished upload of 06oc02ab.7643.20336.678406.1.84_2_0
09/04/2006 17.07.35|SETI@home|Throughput 12609 bytes/sec
09/04/2006 17.07.50|SETI@home|CC calibration: 17.37 >> 7.88 (time: 2965s >> 1345s / Gfpops: 2.29 >> 2.30)
09/04/2006 17.07.50|SETI@home|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
09/04/2006 17.07.50|SETI@home|Reason: Requested by user
09/04/2006 17.07.50|SETI@home|Reporting 1 results
09/04/2006 17.07.55|SETI@home|Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi succeeded
09/04/2006 18.00.03||Rescheduling CPU: application exited
09/04/2006 18.00.03|SETI@home|Computation for result 04oc02ab.9208.3170.579808.1.63_1 finished
09/04/2006 18.00.03|SETI@home|Starting result 04oc02aa.16835.7441.223594.1.82_3 using setiathome version 418
09/04/2006 18.00.03|SETI@home|CC calibration: 17.41 >> 7.90 (time: 2972s >> 1349s / Gfpops: 2.29 >> 2.30)
09/04/2006 18.00.05|SETI@home|Started upload of 04oc02ab.9208.3170.579808.1.63_1_0
09/04/2006 18.00.10|SETI@home|Finished upload of 04oc02ab.9208.3170.579808.1.63_1_0
09/04/2006 18.00.10|SETI@home|Throughput 16516 bytes/sec
09/04/2006 18.09.12|SETI@home|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
09/04/2006 18.09.12|SETI@home|Reason: Requested by user
09/04/2006 18.09.12|SETI@home|Reporting 1 results
09/04/2006 18.09.17|SETI@home|Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi succeeded



che diavolo sarà successo? :confused:



:muro: :muro: :muro: :muro: :muro: :muro: :muro: :muro: :muro: :muro: :muro: :muro: :muro:

hwkiller
09-04-2006, 18:08
Ciao, ne stiamo gia' parlando qui (http://www.hwupgrade.it/forum/showthread.php?t=1150128).

Quei messaggi sono normali, sta' facendo la calibrazione dei crediti x ogni wu elaborata.

Myjungle
09-04-2006, 18:11
ok grazie, però non avevo letto nulla riguardo la diminuzione del tempo di calcolo (magari mi sono perso qualche post :) ).

rimango in attesa di dati migliori!

Grazie Ciao

ConanSeldon
10-04-2006, 08:32
Sta succedendo anche a me.
Comunque attendo che la mod si calibri a dovere e nel frattempo sbircio i post x veder se c'è qualche novità. :D

jarodm
12-04-2006, 11:33
siete pregati di non aprire altri post visto che c'e ne gia uno attivo e molto strutturato

cmq sia dovete lasciarlo al lavoro per qualche giorno minimo 2/3 giorni...il tutto perche deve calibrare i credit :)

ciaooooo

GHz
12-04-2006, 14:03
E allora chiudiamo questo :)