1)
Message boards :
Number crunching :
GUPPI Rescheduler for Linux and Windows - Move GUPPI work to CPU and non-GUPPI to GPU
(Message 1816991)
Posted 14 Sep 2016 by [AF>HFR]yoda51 Post: finaly i notice that my app_info.xml file was 41ko big on the host with probleme and only 11ko big on the 2 other host so i copy one of the smaler file and replace the big 41k file result: resheduling work fine know lot of line with <name>setiathome_v7 and V8 </name> in the big file only <name>setiathome_v8</name> in the smal one |
2)
Message boards :
Number crunching :
GUPPI Rescheduler for Linux and Windows - Move GUPPI work to CPU and non-GUPPI to GPU
(Message 1816956)
Posted 13 Sep 2016 by [AF>HFR]yoda51 Post: Thank everybody for all your answers: I understood that maybe there is no real trouble or file corruption with autotask batch so I will continue to crunch my workunit and NOT reset boinc project please note I run GUPPI Rescheduler v0.4 on two other host frequently (host ID: 7570280 and ID: 8021929 with windows7) without using S@h AutoTaskSwap v0.2_beta1.cmd and that i never got: "Error: could not determine CPU version_num from client_state" even if there was not workunit to resheduled: i got only message "NO non GUPPI assigned to CPU, no change made" "Error: could not determine CPU version_num from client_state. Nothing changed" hapened only on my host ID: 7219793 (using windows 10) and AutoTaskSwap v0.2 and with both version GUPPI Rescheduler v0.4 and v0.51. it hapened more than 10 times one after one, and a few hours later the resheduling was suddenly ok again juste one time. (and always bad since) maybe it could be related on the content of workunit queue .... I notice also that on that host (ID: 7219793) all CPU assigned workunit are GUPPY, but on my GPU's i still have a few GUPPY task on queue after several resheduling attemps |
3)
Message boards :
Number crunching :
GUPPI Rescheduler for Linux and Windows - Move GUPPI work to CPU and non-GUPPI to GPU
(Message 1816886)
Posted 13 Sep 2016 by [AF>HFR]yoda51 Post: hello I try Kevvy's GUPPI rescheduler program and first time it work well then i try S@h AutoTaskSwap v0.2_beta1.cmd because i didn't install boinc on C: i replace in this script c:\ProgramData\BOINC\ with d:\ProgramData\BOINC\ on all lines it seems to work well except i had to restart boinc manualy but I get folowing error: D:\>cd D:\ProgramData\BOINC D:\ProgramData\BOINC>GUPPIRescheduler Mr. Kevvy's GUPPI Rescheduler v0.4 - (c)2016 Kevin Dorner Reading configuration files... Error: could not determine CPU version_num from client_state. Nothing changed. in D:\ProgramData\BOINC\client_state.xml CPU infos are: <host_cpid>b9c18f2db8229ec97fb461192cb143c0</host_cpid> <p_ncpus>4</p_ncpus> <p_vendor>GenuineIntel</p_vendor> <p_model> Intel(R) Core(TM) i5-3570K CPU @ 3.40GHz [Family 6 Model 58 Stepping 9]</p_model> <p_features>fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss htt tm pni ssse3 cx16 sse4_1 sse4_2 popcnt aes f16c rdrandsyscall nx lm avx vmx tm2 pbe fsgsbase smep</p_features> <os_name>Microsoft Windows 10</os_name> <os_version>Professional x64 Edition, (10.00.10586.00)</os_version> -<coprocs> -<coproc_cuda> <count>2</count> <name>GeForce GTX 1060 3GB</name> <available_ram>2651740569.000000</available_ram> S@h AutoTaskSwap v0.2_beta1 is copying several time that file (copy /Y d:\ProgramData\BOINC\client_state.xml .\client_state-backup.xml>nul) maybe a corruption occurs ? i think i will restart seti project/resintall boinc after crunshing all workunit in place.... any suggestion is wellcome... |
4)
Message boards :
Number crunching :
Fred's Rescheduler and V7
(Message 1378724)
Posted 8 Jun 2013 by [AF>HFR]yoda51 Post: Do you known if there will be a new version of the boinc work resheduler compatible with seti V7 ? vlar WU should never send to GPU (cuda) and i can see a very high drop of calulation effiency with seti V7 http://boincstats.com/signature/-1/user/1210/sig.png |
5)
Message boards :
Number crunching :
20% average of WU drop since using V7
(Message 1378126)
Posted 7 Jun 2013 by [AF>HFR]yoda51 Post: la distribution des tâches ne me semble pas fortement ralentie en ce moment j'ai meme plus de WU que dans la version précedente ! Sinon pour améliorer la lenteur des downloads ou le peu de reponse positives du serveur lorsque votre stock de wu est faible, il suffit de créer un fichier cc_config.xml dans BOINC DATA\projects\setiathome.berkeley.edu avec le contenu suivant: <cc_config> <options> <max_file_xfers>16</max_file_xfers> <max_file_xfers_per_project>16</max_file_xfers_per_project> </options> </cc_config> aulieu de 2 downloads simultanés vous en aurez 16 ! |
6)
Message boards :
Number crunching :
20% average of WU drop since using V7
(Message 1377841)
Posted 7 Jun 2013 by [AF>HFR]yoda51 Post: since I use seti version 7 (with same lunatics optimized binary than on previous version): Lunatics_x41zc_win32_cuda42.exe (GPU FERMI) AKv8c_Bb_r1846_winx86_SSSE3x.exe (CPU) my average of work unit completed has drop over 20% !! (from 55000 to 40000 credit !!!) the only difference is i can not use anymore boinc resheduler 2.7 with V7 to assign vlar bloc to CPU do you have any explanation or solution for that ? |
7)
Message boards :
Number crunching :
Just some early observations on V7 CUDA work.
(Message 1377838)
Posted 7 Jun 2013 by [AF>HFR]yoda51 Post: since I use seti version 7 my average of work unit with same optimized binary: Lunatics_x41zc_win32_cuda42.exe (GPU FERMI) AKv8c_Bb_r1846_winx86_SSSE3x.exe (CPU) has drop over 20% !! (from 55000 to 40000 credit !!!) the only difference is i can not use anymore boinc resheduler 2.7 with V7 to assign vlar bloc to CPU do you have any explanation or solution for that ? |
8)
Questions and Answers :
GPU applications :
Problem with Geforce GTX 560 Ti and Cuda_fermi
(Message 1116375)
Posted 12 Jun 2011 by [AF>HFR]yoda51 Post: I saw that the half speed BUG on GTX560TI (440mhz instead of 880mhz) in case of manual overclock (factory default speed is 880mhz) is not really corrected with use of the oldest NVIDIA compatible driver 266.66 And previous driver 266.58 is not working on GTX560 but is ok on GTX460 Since I realize that, i dont overclock at all my GTX560TI and reboot the PC to restore a real 880mhz speed my GTX560TI is a twin froz II modele from MSI capable to run at 1,1Ghz !! I hope that some one will fix that bug so i will be able to use the full power of that recent GPU with a good overclock for crunching !! |
9)
Questions and Answers :
GPU applications :
Problem with Geforce GTX 560 Ti and Cuda_fermi
(Message 1116180)
Posted 12 Jun 2011 by [AF>HFR]yoda51 Post: I own 3 GTX460 and one GTX560TI on GTX460 I saw no probleme using NVIDIA driver 266.58 and Lunatics_Win32v0.37_AP505r409_AKv8b_Cudax32f BUG: on GTX560TI with NVIDIA driver 275.33 and lunatics_Win32v0.37_AP505r409_AKv8b_Cudax32f, the GPU was only 40 degré while crunching WU and GPU-Z_ASUS_ROG_0.5.3 report a frequency of 440mhz instead of 880mhz ! even on my old 9800GT crunching results were better than on my new FERMI GTX560TI card. Maybe this BUG is related to the new CUDA compute capabilities in the NIDIA serie of driver 27xxx ! SOLUTION: I install the oldest NVIDIA driver 266.66 compatible with my GTX560TI and it's work fine full speed all time now ! |
10)
Questions and Answers :
GPU applications :
Problem with Geforce GTX 560 Ti and Cuda_fermi
(Message 1106576)
Posted 15 May 2011 by [AF>HFR]yoda51 Post: thank for the answer but i solve my problem with GTX560TI doing this: 1) restoring my windows system partition using clonezilla USB version 2) uninstalling boinc 3) removing all my boinc files 4) reinstalling boinc official version wu ok 5) reinstalling lunatics fermi application (Lunatics_Win32v0.37_AP505r409_AKv8b_Cudax32f.exe) wu calculations complet well now even by using resheduler for VHAR VLAR wu (boinc_rescheduler_2_5.zip) have a nice day |
11)
Questions and Answers :
GPU applications :
Problem with Geforce GTX 560 Ti and Cuda_fermi
(Message 1106478)
Posted 15 May 2011 by [AF>HFR]yoda51 Post: i also buy a GTX560TI and replace a GTX285 i checked the GTX560TI with somes games and a stability utily: VideoCardStabilityTestSetup.exe hardware is OK after reinstall boinc and i get also all my SETI@home WU finish in a couple of seconds without error in 1 hour time the GTX560TI finished calculating more than 1000 WU !! what the trouble ? i run 2 GPU instances and re install BOINC with official binary: setigraphics_6.03_windows_intelx86.exe cudart32_30_14.dll setiathome_6.03_windows_intelx86.exe libfftw3f-3-1-1a_upx.dll setiathome_6.10_windows_intelx86__cuda_fermi.exe cufft32_30_14.dll same result 1000wu in one hour on GTX560TI i replace GTX560TI with the GTX285 everything is normal again (1 Wu in 20mn) even with optimized binaries: MB_6.08_CUDA_V12_VLARKill_FPLim2048.exe AK_v8b_win_SSSE3x.exe libfftw3f-3-1-1a_upx.dll cufft.dll AKv8SSSE3x.aistub how can i solve this ? my app_info.xml looks like that: <app_info> <app> <name>setiathome_enhanced</name> </app> <file_info> <name>AK_v8b_win_SSSE3x.exe</name> <executable/> </file_info> <app_version> <app_name>setiathome_enhanced</app_name> <version_num>603</version_num> <file_ref> <file_name>AK_v8b_win_SSSE3x.exe</file_name> <main_program/> </file_ref> </app_version> <app> <name>setiathome_enhanced</name> </app> <file_info> <name>MB_6.08_CUDA_V12_VLARKill_FPLim2048.exe</name> <executable/> </file_info> <file_info> <name>cudart.dll</name> <executable/> </file_info> <file_info> <name>cufft.dll</name> <executable/> </file_info> <file_info> <name>libfftw3f-3-1-1a_upx.dll</name> <executable/> </file_info> <app_version> <app_name>setiathome_enhanced</app_name> <version_num>608</version_num> <plan_class>cuda</plan_class> <avg_ncpus>0.040000</avg_ncpus> <max_ncpus>0.040000</max_ncpus> <coproc> <type>CUDA</type> <count>0.5</count> </coproc> <file_ref> <file_name>MB_6.08_CUDA_V12_VLARKill_FPLim2048.exe</file_name> <main_program/> </file_ref> <file_ref> <file_name>cudart.dll</file_name> </file_ref> <file_ref> <file_name>cufft.dll</file_name> </file_ref> <file_ref> <file_name>libfftw3f-3-1-1a_upx.dll</file_name> </file_ref> </app_version> <app_version> <app_name>setiathome_enhanced</app_name> <version_num>608</version_num> <plan_class>cuda23</plan_class> <avg_ncpus>0.040000</avg_ncpus> <max_ncpus>0.040000</max_ncpus> <coproc> <type>CUDA</type> <count>0.5</count> </coproc> <file_ref> <file_name>MB_6.08_CUDA_V12_VLARKill_FPLim2048.exe</file_name> <main_program/> </file_ref> <file_ref> <file_name>cudart.dll</file_name> </file_ref> <file_ref> <file_name>cufft.dll</file_name> </file_ref> <file_ref> <file_name>libfftw3f-3-1-1a_upx.dll</file_name> </file_ref> </app_version> </app_info> |
©2024 University of California
SETI@home and Astropulse are funded by grants from the National Science Foundation, NASA, and donations from SETI@home volunteers. AstroPulse is funded in part by the NSF through grant AST-0307956.