|
1)
Message boards :
Number crunching :
raspberry pi 2
(Message 764)
Posted 5 May 2015 by NATE1 Post: thanks just wanted to see if you were going to do an app for arm version 7 linux for the raspberry pi 2 |
|
2)
Message boards :
Number crunching :
raspberry pi 2
(Message 761)
Posted 4 May 2015 by NATE1 Post: do you have plans for a r pi 2 app? RASPBIAN version... |
|
3)
Message boards :
Number crunching :
44 h running and still going, should I abort
(Message 652)
Posted 19 Mar 2014 by NATE1 Post: According to the server settings you can report a result up to 120 hours after the deadline and will get credits for it. hate to tell you this but yesterday I had a number of task that aborted with 203(?) 48 hours and 10 minutes after the deadline. I did not abort them the project server did that. I was going to just let them run till they got done. so the 120 hours your see is wrong or there is something misconfigured on it. because I would have let them run till the end of time if need be because they were running. but we shall see I have some tasks that have been running for over 2 days and the deadline was due today so if they are still running on the 21st at 48 hours 10 minutes past deadline and the server aborts them. oh well........ edit: didn't you post when when you updated to the latest(?) that for a while no work was being sent out? maybe this has something to do with it? |
|
4)
Message boards :
Number crunching :
44 h running and still going, should I abort
(Message 649)
Posted 19 Mar 2014 by NATE1 Post: Hello, I have a workunit, that is computing more than 45 hours. It is workunit: 48 hours and 10 minutes after the deadline the server will kill off the task. only your host(computer) will know for sure if it will make it by that time. so if it is not too far past the deadline let it run. but it it is getting close to deadline + 48 hours than you have to choose. wait it out or abort it.. I know it's 48 hours and 10 minutes, because I had some tasks that had been running for over 3 and 1/2 days and the server aborted them as unuseable only because they were 48 hours pasted the deadline. they were still running and may have finished if given the chance. |
|
5)
Message boards :
Number crunching :
why does it need all 8 cores to run
(Message 635)
Posted 6 Feb 2014 by NATE1 Post: and in case your wondering if you change that app_config.xml to the following it will run like a ST task. just remember that when the yafu-x64-13401.exe is running ( that is on a 64 bit windows host) it will still try and use all of the cores, but that is for very short times, the avg_ncups and --nthreads part control the number of copies of the ecm and gnfs that it will start.. <!-- YAFU --> <app_config> <!-- YAFU --> <!-- YAFU --> <app_version> <app_name>yafu</app_name> <plan_class>mt</plan_class> <avg_ncpus>1</avg_ncpus> <cmdline>--nthreads 1</cmdline> </app_version> </app_config> |
|
6)
Message boards :
Number crunching :
why does it need all 8 cores to run
(Message 634)
Posted 5 Feb 2014 by NATE1 Post: there is another way now. download boinc version 7.2.39, it's beta but works.. install. create the following app_config.xml in the yafu directory. use text editor this will over ride using up all of the cores.in this case it limits the number of threads to 2. so it does not keep your gpu projects apps from running or other ST apps from other projects that are getting close to deadline... it also lets you run more than one yafu task at a time. I did not come up with this, found it over on MW@H, a great big thank you to the person that posted it over on MW@H.. after you create the app_config.xml you will need to stop the BOINC client and restart for it to take effect... <!-- YAFU --> <app_config> <!-- YAFU --> <!-- YAFU --> <app_version> <app_name>yafu</app_name> <plan_class>mt</plan_class> <avg_ncpus>2</avg_ncpus> <cmdline>--nthreads 2</cmdline> </app_version> </app_config> |
|
7)
Message boards :
Number crunching :
server side config.xml, N
(Message 572)
Posted 30 Jun 2013 by NATE1 Post: also <avg_ncpus>8.000000</avg_ncpus> will need to be changed to <avg_ncpus>2.000000</avg_ncpus> |
|
8)
Message boards :
Number crunching :
server side config.xml, N
(Message 571)
Posted 30 Jun 2013 by NATE1 Post: <max_ncpus>N</max_ncpus> An upper bound on NCPUS (default: 64) (which is why during the test I never got past 64 threads) http://boinc.berkeley.edu/trac/wiki/ProjectOptions read N from On multiprocessors, use at most 2 processors from When and how BOINC uses your computer Computing preferences N=setting in this case the on multipro.... use at most 2 processor therefor N is replaced with 2. yafujobmt_0.04.xml <job_desc> <task> <application>yafu</application> <stdout_filename>out</stdout_filename> <command_line>-threads "2" -batchfile in</command_line> <multi_process/> <checkpoint_filename>nfs.dat</checkpoint_filename> </task> </job_desc> or however you change a dynamic argument to a static $NTHREADS=2 client_state.xml would look like app_version> <app_name>yafu</app_name> <version_num>13401</version_num> <platform>windows_x86_64</platform> <avg_ncpus>8.000000</avg_ncpus> <max_ncpus>2.000000</max_ncpus> <flops>21017886472.298004</flops> <plan_class>mt</plan_class> <api_version>7.1.0</api_version> <cmdline>--nthreads 2</cmdline> <file_ref> <file_name>yafuwrapper_26002_windows_x86_64.exe</file_name> <main_program/> </file_ref> <file_ref> <file_name>yafujobmt_0.04.xml</file_name> <open_name>job.xml</open_name> </file_ref> <file_ref> <file_name>yafu-x64-13401.exe</file_name> <open_name>yafu</open_name> <copy_file/> </file_ref> <file_ref> <file_name>yafu_w64mt_02.ini</file_name> <open_name>yafu.ini</open_name> <copy_file/> </file_ref> <file_ref> <file_name>ecm63mpir230core2-64.exe</file_name> <open_name>ecm.exe</open_name> <copy_file/> </file_ref> <file_ref> <file_name>gnfs-lasieve4I11e_w64_01.exe</file_name> <open_name>gnfs-lasieve4I11e.exe</open_name> <copy_file/> </file_ref> <file_ref> <file_name>gnfs-lasieve4I12e_w64_01.exe</file_name> <open_name>gnfs-lasieve4I12e.exe</open_name> <copy_file/> </file_ref> <file_ref> <file_name>gnfs-lasieve4I13e_w64_01.exe</file_name> <open_name>gnfs-lasieve4I13e.exe</open_name> <copy_file/> </file_ref> <file_ref> <file_name>gnfs-lasieve4I14e_w64_01.exe</file_name> <open_name>gnfs-lasieve4I14e.exe</open_name> <copy_file/> </file_ref> <file_ref> <file_name>gnfs-lasieve4I15e_w64_01.exe</file_name> <open_name>gnfs-lasieve4I15e.exe</open_name> <copy_file/> </file_ref> <file_ref> <file_name>gnfs-lasieve4I16e_w64_01.exe</file_name> <open_name>gnfs-lasieve4I16e.exe</open_name> <copy_file/> </file_ref> </app_version> sounds easy but, then I'm not a programmer. :) |
|
9)
Message boards :
Number crunching :
Processing while time remain is 0
(Message 568)
Posted 23 Jun 2013 by NATE1 Post: when a task in the manager show time remaining '--' the boinc client start counting negative time. ie 60 seconds after the time remaining show '--' it is counted as -60 seconds or negative 60 seconds. this confuses the boinc client when doing the calculations as to how much work to request from the projects. if a task has been setting at time remaining for 1 hour with '--' showing in the time remaining field than that counts as -3600 seconds. adding up all the time remaining from all the tasks then subtracting the the total run time for the projects that show '--' will cause the boinc client work request to be higher than it should be, causing tasks to go into running, high pri... status. therefor missing deadline on other tasks for other projects. keeping the time remaining above 2 minutes will keep the boinc client from requesting more work. how you deal with this is up to you. Toki nokori manējashōtaimu de tasuku' - ' fu no jikan o kaunto BOINC kuraianto o kaishi. 60-Byō nokori jikan shō no ato sunawachi' - ' soreha - 60-byō negatibu 60-byō to shite kaunto sa remasu. Purojekuto kara yōkyū suru yō ni hatarakuto dono kurai made no yōna keisan o jikkō suru toki ni, koreha BOINC kuraianto o konran sa seru. Tasuku ga tsuite iru 1-jikan no nokori jikan ni settei sa rete iru baai wa' - ' - 3600-byō to shite sono kaunto mo nokori jikan fīrudo ni hyōji. Tsugini shimesu purojekuto no sō jikkō jikan o hiita subete no tasuku kara nokori subete no jikan o tsuika shi, ' - ' ga BOINC kuraianto no shigoto no yōkyū wa tasuku ga, takai PRI o jikkō shite hairu koto o hikiokoshite, sore ga arubeki yori mo takaku naru yō ni narimasu ... Sutētasu. Sonotame, hoka no purojekuto no tame ni, hoka no tasuku ni kigen o yukue fumei. 2-Bu jōki no nokori jikan o hoji suru koto wa, yori ōku no sagyō o yōkyū surukara BOINC kuraianto o iji shimasu. Anata ga taisho hōhō kore wa anata shidaidesu. 01110111 01101000 01100101 01101110 00100000 01100001 00100000 01110100 01100001 01110011 01101011 00100000 01101001 01101110 00100000 01110100 01101000 01100101 00100000 01101101 01100001 01101110 01100001 01100111 01100101 01110010 00100000 01110011 01101000 01101111 01110111 00100000 01110100 01101001 01101101 01100101 00100000 01110010 01100101 01101101 01100001 01101001 01101110 01101001 01101110 01100111 00100000 01011100 00100111 00101101 00101101 01011100 00100111 00100000 01110100 01101000 01100101 00100000 01100010 01101111 01101001 01101110 01100011 00100000 01100011 01101100 01101001 01100101 01101110 01110100 00100000 01110011 01110100 01100001 01110010 01110100 00100000 01100011 01101111 01110101 01101110 01110100 01101001 01101110 01100111 00100000 01101110 01100101 01100111 01100001 01110100 01101001 01110110 01100101 00100000 01110100 01101001 01101101 01100101 00101110 00100000 01101001 01100101 00100000 00110110 00110000 00100000 01110011 01100101 01100011 01101111 01101110 01100100 01110011 00100000 01100001 01100110 01110100 01100101 01110010 00100000 01110100 01101000 01100101 00100000 01110100 01101001 01101101 01100101 00100000 01110010 01100101 01101101 01100001 01101001 01101110 01101001 01101110 01100111 00100000 01110011 01101000 01101111 01110111 00100000 01011100 00100111 00101101 00101101 01011100 00100111 00100000 01101001 01110100 00100000 01101001 01110011 00100000 01100011 01101111 01110101 01101110 01110100 01100101 01100100 00100000 01100001 01110011 00100000 00101101 00110110 00110000 00100000 01110011 01100101 01100011 01101111 01101110 01100100 01110011 00100000 01101111 01110010 00100000 01101110 01100101 01100111 01100001 01110100 01101001 01110110 01100101 00100000 00110110 00110000 00100000 01110011 01100101 01100011 01101111 01101110 01100100 01110011 00101110 00100000 01110100 01101000 01101001 01110011 00100000 01100011 01101111 01101110 01100110 01110101 01110011 01100101 01110011 00100000 01110100 01101000 01100101 00100000 01100010 01101111 01101001 01101110 01100011 00100000 01100011 01101100 01101001 01100101 01101110 01110100 00100000 01110111 01101000 01100101 01101110 00100000 01100100 01101111 01101001 01101110 01100111 00100000 01110100 01101000 01100101 00100000 01100011 01100001 01101100 01100011 01110101 01101100 01100001 01110100 01101001 01101111 01101110 01110011 00100000 01100001 01110011 00100000 01110100 01101111 00100000 01101000 01101111 01110111 00100000 01101101 01110101 01100011 01101000 00100000 01110111 01101111 01110010 01101011 00100000 01110100 01101111 00100000 01110010 01100101 01110001 01110101 01100101 01110011 01110100 00100000 01100110 01110010 01101111 01101101 00100000 01110100 01101000 01100101 00100000 01110000 01110010 01101111 01101010 01100101 01100011 01110100 01110011 00101110 01101 01010 01101001 01100110 00100000 01100001 00100000 01110100 01100001 01110011 01101011 00100000 01101000 01100001 01110011 00100000 01100010 01100101 01100101 01101110 00100000 01110011 01100101 01110100 01110100 01101001 01101110 01100111 00100000 01100001 01110100 00100000 01110100 01101001 01101101 01100101 00100000 01110010 01100101 01101101 01100001 01101001 01101110 01101001 01101110 01100111 00100000 01100110 01101111 01110010 00100000 00110001 00100000 01101000 01101111 01110101 01110010 00100000 01110111 01101001 01110100 01101000 00100000 01011100 00100111 00101101 00101101 01011100 00100111 00100000 01110011 01101000 01101111 01110111 01101001 01101110 01100111 00100000 01101001 01101110 00100000 01110100 01101000 01100101 00100000 01110100 01101001 01101101 01100101 00100000 01110010 01100101 01101101 01100001 01101001 01101110 01101001 01101110 01100111 00100000 01100110 01101001 01100101 01101100 01100100 00100000 01110100 01101000 01100001 01101110 00100000 01110100 01101000 01100001 01110100 00100000 01100011 01101111 01110101 01101110 01110100 01110011 00100000 01100001 01110011 00100000 00101101 00110011 00110110 00110000 00110000 00100000 01110011 01100101 01100011 01101111 01101110 01100100 01110011 00101110 01101 01010 01100001 01100100 01100100 01101001 01101110 01100111 00100000 01110101 01110000 00100000 01100001 01101100 01101100 00100000 01110100 01101000 01100101 00100000 01110100 01101001 01101101 01100101 00100000 01110010 01100101 01101101 01100001 01101001 01101110 01101001 01101110 01100111 00100000 01100110 01110010 01101111 01101101 00100000 01100001 01101100 01101100 00100000 01110100 01101000 01100101 00100000 01110100 01100001 01110011 01101011 01110011 00100000 01110100 01101000 01100101 01101110 00100000 01110011 01110101 01100010 01110100 01110010 01100001 01100011 01110100 01101001 01101110 01100111 00100000 01110100 01101000 01100101 00100000 01110100 01101000 01100101 00100000 01110100 01101111 01110100 01100001 01101100 00100000 01110010 01110101 01101110 00100000 01110100 01101001 01101101 01100101 00100000 01100110 01101111 01110010 00100000 01110100 01101000 01100101 00100000 01110000 01110010 01101111 01101010 01100101 01100011 01110100 01110011 00100000 01110100 01101000 01100001 01110100 00100000 01110011 01101000 01101111 01110111 00100000 01011100 00100111 00101101 00101101 01011100 00100111 00100000 01110111 01101001 01101100 01101100 00100000 01100011 01100001 01110101 01110011 01100101 00100000 01110100 01101000 01100101 00100000 01100010 01101111 01101001 01101110 01100011 00100000 01100011 01101100 01101001 01100101 01101110 01110100 00100000 01110111 01101111 01110010 01101011 00100000 01110010 01100101 01110001 01110101 01100101 01110011 01110100 00100000 01110100 01101111 00100000 01100010 01100101 00100000 01101000 01101001 01100111 01101000 01100101 01110010 00100000 01110100 01101000 01100001 01101110 00100000 01101001 01110100 00100000 01110011 01101000 01101111 01110101 01101100 01100100 00100000 01100010 01100101 00101100 00100000 01100011 01100001 01110101 01110011 01101001 01101110 01100111 00100000 01110100 01100001 01110011 01101011 01110011 00100000 01110100 01101111 00100000 01100111 01101111 00100000 01101001 01101110 01110100 01101111 00100000 01110010 01110101 01101110 01101110 01101001 01101110 01100111 00101100 00100000 01101000 01101001 01100111 01101000 00100000 01110000 01110010 01101001 00101110 00101110 00101110 00100000 01110011 01110100 01100001 01110100 01110101 01110011 00101110 00100000 01110100 01101000 01100101 01110010 01100101 01100110 01101111 01110010 00100000 01101101 01101001 01110011 01110011 01101001 01101110 01100111 00100000 01100100 01100101 01100001 01100100 01101100 01101001 01101110 01100101 00100000 01101111 01101110 00100000 01101111 01110100 01101000 01100101 01110010 00100000 01110100 01100001 01110011 01101011 01110011 00100000 01100110 01101111 01110010 00100000 01101111 01110100 01101000 01100101 01110010 00100000 01110000 01110010 01101111 01101010 01100101 01100011 01110100 01110011 00101110 01101 01010 01101011 01100101 01100101 01110000 01101001 01101110 01100111 00100000 01110100 01101000 01100101 00100000 01110100 01101001 01101101 01100101 00100000 01110010 01100101 01101101 01100001 01101001 01101110 01101001 01101110 01100111 00100000 01100001 01100010 01101111 01110110 01100101 00100000 00110010 00100000 01101101 01101001 01101110 01110101 01110100 01100101 01110011 00100000 01110111 01101001 01101100 01101100 00100000 01101011 01100101 01100101 01110000 00100000 01110100 01101000 01100101 00100000 01100010 01101111 01101001 01101110 01100011 00100000 01100011 01101100 01101001 01100101 01101110 01110100 00100000 01100110 01110010 01101111 01101101 00100000 01110010 01100101 01110001 01110101 01100101 01110011 01110100 01101001 01101110 01100111 00100000 01101101 01101111 01110010 01100101 00100000 01110111 01101111 01110010 01101011 00101110 01101 01010 01101000 01101111 01110111 00100000 01111001 01101111 01110101 00100000 01100100 01100101 01100001 01101100 00100000 01110111 01101001 01110100 01101000 00100000 01110100 01101000 01101001 01110011 00100000 01101001 01110011 00100000 01110101 01110000 00100000 01110100 01101111 00100000 01111001 01101111 01110101 00101110 |
|
10)
Message boards :
Number crunching :
What is this?!
(Message 566)
Posted 17 Jun 2013 by NATE1 Post:
nope, did not need 10,000. running a test to see just how many threads really started up. it max'es out at 64. so host with 64 real/HT type cpus can really do well. I'm done testing and have put everything back to normal. I do know letting it start all 64 threads even on a 2/4 core host it had lower run times. the AMD running with 2 cpus/threads was still running after 26 hours, 64 threads took about 19. same task. system rebooted after 26 hours so I set it up for 64 threads. but, you had better not do it, you can't really control the number of tasks that get downloaded! as far as the credits go maybe the 1st 1 or 2 payed well, but then the credit system kicked in and ripped the heck out of the payout. anyway, done, again don't do it unless your willing to have a fubar on you. |
|
11)
Message boards :
Number crunching :
Windows Error
(Message 553)
Posted 31 May 2013 by NATE1 Post: try running this on yafu app http://www.dependencywalker.com/ |
|
12)
Message boards :
Number crunching :
unit should be in panic, but not
(Message 540)
Posted 21 Mar 2013 by NATE1 Post: Hi no. it's boinc. |
|
13)
Message boards :
Number crunching :
Too Late To Validate
(Message 386)
Posted 16 Mar 2012 by NATE1 Post: yafu_C106_1331495706_321_0 missing from web site still on computer running at time of post. since it is not on the web site and the host runs it out will it be usable to you? I have no problem. |
|
14)
Message boards :
Number crunching :
Too Late To Validate
(Message 382)
Posted 15 Mar 2012 by NATE1 Post: the following is a list of work units on your web site yafu_C106_1331746208_332_0 yafu_C106_1331746208_318_0 yafu_C106_1331746208_256_0 yafu_C106_1331746208_184_0 yafu_C106_1331746208_173_0 yafu_C106_1331495706_349_0 yafu_C106_1331495706_337_0 yafu_C106_1331495706_303_0 yafu_C106_1331495706_283_0 yafu_C106_1331495706_263_0 yafu_C106_1331495706_231_0 yafu_C106_1331495706_197_0 yafu_C106_1331495706_79_0 yafu_C106_1331495706_71_0 yafu_C106_1331463909_469_0 up until about an hour or 2 ago I had 2 tasks that were still running on the hosts but were past deadline and flag as red on the website. one of these was: yafu_C106_1331495706_321_0 now it gone off the website but it's still running on the host. is this a lost cause or let it run? |
|
15)
Message boards :
Number crunching :
long cpu times
(Message 380)
Posted 15 Mar 2012 by NATE1 Post: looks like we need a project just to figure out the number of years that is. been Time traveling? |
|
16)
Message boards :
Number crunching :
server time
(Message 332)
Posted 31 Jan 2012 by NATE1 Post: your server time stamp is now 4 hours faster than utc time. how fast was the crystal you soldered in place in your system's oscillator to get it to clock fast 1 hour for every 23? the good old day, overclock an IBM pc stock 4.77 Mhz to 5.00 Mhz. ;) |
|
17)
Message boards :
Number crunching :
need app_info.xml stuff for non-MT app
(Message 331)
Posted 30 Jan 2012 by NATE1 Post: You have them already ;) it look like all you have to do is have the project set(or not set) the -threads flag in the job.xml according to the above. DA may have not know at the time DA answered. my $0.02 |
|
18)
Message boards :
Number crunching :
need app_info.xml stuff for non-MT app
(Message 329)
Posted 29 Jan 2012 by NATE1 Post: maybe an option in: Preferences for this project :to run mt or not run mt, project T4T has it |
|
19)
Message boards :
Number crunching :
server time
(Message 293)
Posted 13 Jan 2012 by NATE1 Post: thanks, but your still over 1 hour off UTC. |
|
20)
Message boards :
Number crunching :
server time
(Message 291)
Posted 11 Jan 2012 by NATE1 Post: when is the last time the server time was sync'ed to standard utc reference? |