1) Message boards : Number crunching : How is the SSE3 thing coming along? (Message 24337)
Posted 13 Jul 2012 by achim.huber
Post:
13.07.2012 13:24:49 | LHC@home 1.0 | Aborting task w1jul_niebb1d__39__s__64.28_59.31__9.8_10__6__28_1_sixvf_boinc68469_1: exceeded elapsed time limit 13518.14 (1800000.00G/133.15G)
13.07.2012 13:38:26 | LHC@home 1.0 | Aborting task w1jul_niebb1d__39__s__64.28_59.31__9.8_10__6__24_1_sixvf_boinc68465_1: exceeded elapsed time limit 13518.14 (1800000.00G/133.15G)
13.07.2012 13:49:34 | LHC@home 1.0 | Aborting task w1jul_niebb1d__39__s__64.28_59.31__9.8_10__6__26_1_sixvf_boinc68467_1: exceeded elapsed time limit 13518.14 (1800000.00G/133.15G)
13.07.2012 13:59:44 | LHC@home 1.0 | Aborting task w1jul_niebb1d__39__s__64.28_59.31__9.8_10__6__25_1_sixvf_boinc68466_1: exceeded elapsed time limit 13518.14 (1800000.00G/133.15G)
13.07.2012 17:23:46 | LHC@home 1.0 | Aborting task w1jul_niebb1d__39__s__64.28_59.31__9.8_10__6__30_1_sixvf_boinc68471_1: exceeded elapsed time limit 13518.14 (1800000.00G/133.15G)

Why is there a time limit that makes it impossible to finish a Workunit? I've set BOINC to "No new Tasks" until this gets sorted out.
2) Message boards : Number crunching : How is the SSE3 thing coming along? (Message 24331)
Posted 13 Jul 2012 by achim.huber
Post:
I received 8 SSE3 WUs. All ended in a calculation error after a runtime of 13,518 seconds.
3) Message boards : Number crunching : sixtrack 4.67 (Message 13365)
Posted 14 Apr 2006 by achim.huber
Post:

[/quote]

The strange thing is Benchmarking shows the same results whenever Cool'n'Quiet is off or on. But still crunches two times faster...

[/quote]

I don't use Cool'n'Quiet because this feature only helps when the processor doesn't do anything and I always run BOINC when my Computer is on.
The reason that BOINC Benchmarks are the same is that BOINC runs with normal priority. So even with Cool'n'Quiet turned on the processor runs with full speed. The science apps run with lowest priority and with Cool'n'Quiet turned on your processor only runs with 1 GHz instead of 2 GHz.
4) Message boards : Number crunching : sixtrack 4.67 (Message 13353)
Posted 13 Apr 2006 by achim.huber
Post:
Is there an optimized client for LHC like there is for SETI or is it not optimizable?


No. They won't make an optimized client because thy need very accurate results.
5) Message boards : Number crunching : sixtrack 4.67 (Message 13351)
Posted 13 Apr 2006 by achim.huber
Post:
I'm jumping in with the similar question. Recently I've upgraded to Athlon 64 3800+ Dual core. Normal WU now takes 5 hour 20 minutes to complete on each core. This looks extremely slow for me, especially comparing with my old Athlon 1300. Is it normal? I'm using BOINC 5.2.13 and Win2K SP4.

Best Regards,
Andrew


It is extremly slow. I have also a Athlon 64 X2 3800+ using BOINC 5.2.13 and WinXP SP2. A normal WU should take 3 hours on each core.



©2024 CERN