Posts by Sutaru Tsureku

41) Message boards : News : N-body updated to 0.80 (Message 51962) Posted 13 Dec 2011 by Sutaru Tsureku Post: Additional.. little bit off topic.. sorry. Since I calculate MW@h WUs, I find it a pity that on my E7600 + GTX260 I have max 12 WUs/whole machine. It's 6 WUs/CPU(-thread), right? It's possible to make it little bit better? CPU and GPU WU limit in progress separately? In past, sometimes I have 12 CPU WUs and no GPU WUs in BOINC, because of the combined WU limit in progress. There I needed to un-/check always the CPU in the project settings, for to have CPU and GPU busy - very cumbersome.. It would be nice to have a CPU and GPU WU limit in progress separately here at MW@h. E.g. currently S@h have 50 WUs/CPU(-thread) and 400 WUs/GPU (limit of tasks in progress). So I guess here at MW@h it could be also possible (if the server software is the same). ;-) I don't mean the same limit, maybe 12 WUs/GPU and 4 WUs/CPU(-thread). But if currently the n-body lasts only 10 seconds.. then maybe currently also 12 WUs/CPU(-thread).
42) Message boards : News : N-body updated to 0.80 (Message 51960) Posted 13 Dec 2011 by Sutaru Tsureku Post: So I understand correct, at Duo CPUs (2 threads) the whole CPU is used for one n-body WU? BOINC said 2 CPUs. (After looking to client_state.xml there are entries: <avg_ncpus>2.000000</avg_ncpus> and <max_ncpus>2.000000</max_ncpus>) Or all n-body CPU WUs need 2 threads, independent which CPU? Is really the whole CPU @ 100 % used (Duo CPU), or it's only a calculation thing for BOINC how to calculate the WU cache? It was too fast for me to look in Task Manager. If BOINC say 2 CPUs/1 WU for n-body, then the GPU stop the calculation, because stock it's 0.05 CPU/1 GPU for the MW@h GPU WUs. So maybe it's possible to cancel the thread usage for CPU WUs (upper mentioned entries)? So the GPU wouldn't stop the calculation.
43) Message boards : News : N-body updated to 0.80 (Message 51953) Posted 13 Dec 2011 by Sutaru Tsureku Post: My machine (E7600 + GTX260) got a few N-Body Simulation v0.80 (mt) WUs, all finished after ~ 10 seconds. Got credits for it. So I guess they were well. http://milkyway.cs.rpi.edu/milkyway/result.php?resultid=43607717 Online they are named: MilkyWay@Home N-Body Simulation v0.80 (mt) The Stderr output: <core_client_version>6.12.33</core_client_version> <![CDATA[ <stderr_txt> <search_application> milkyway_nbody_0.80_windows_x86_64__mt.exe 0.80 Windows x86 double OpenMP, Crlibm </search_application> Using OpenMP 2 max threads on a system with 2 processors Could not load Ktm32.dll (1815): (null)<search_likelihood>-85.378413103860581</search_likelihood> 17:55:31 (1508): called boinc_finish </stderr_txt> ]]> Named 64bit app? In the MW@h project folder is the milkyway_nbody_0.80_windows_intelx86__mt.exe app. In BOINC it was shown that 2 CPUs are used for 1 WU. (no app_info.xml file, all stock) Everything O.K. here?
44) Message boards : Number crunching : only v0.82 cuda_opencl app errors (Message 51664) Posted 11 Nov 2011 by Sutaru Tsureku Post: I looked through the results of my machine and found a (wingman) machine which make only v0.82 cuda_opencl app errors. hostid=212443 Maybe someone know what's wrong there? I have not much experiences with MW@h.. If I look to the hosts app overview.. the _x86_64 app ran well. If the reason was found, maybe someone could info the owner..
45) Message boards : News : Nvidia OpenCL updated (Message 46240) Posted 14 Feb 2011 by Sutaru Tsureku Post: Please read this http://milkyway.cs.rpi.edu/milkyway/forum_thread.php?id=1505&nowrap=true#46230 Cuda should still work. BTW. IIRC, this isn't the stock 0.24_cuda23 app of MW@h. It's Crunch3r's Fermi mod which have arkayn on his DL site. But I guess the stock 0.24_cuda23 app of MW@h should work then on old </= GTX2xx GPUs. But it would be nice to know from an admin, if it's still allowed to use the stock/mod CUDA23 app.
46) Message boards : News : Nvidia OpenCL updated (Message 46239) Posted 14 Feb 2011 by Sutaru Tsureku Post: Thanks for info. But now I'm confused and I get the question, why published MW@h a new nVIDIA app (OpenCL) and the old nVIDIA app (CUDA23) crunch happy the currently WUs? The new nVIDIA OpenCL app use the whole Fermi chip (GTX4xx/5xx)? Maybe an admin of MW@h could answer if it's allowed to use still the old nVIDIA CUDA23 app (which would be the only way for me to crunch MW@h)? Thanks. Maybe it's possible to send out the old CUDA23 app to hosts with < 197.x driver and the new OpenCL app to hosts with >/= 197.x driver?
47) Message boards : News : Nvidia OpenCL updated (Message 46231) Posted 14 Feb 2011 by Sutaru Tsureku Post: Ohh.. a pity, MW@h canceled the CUDA apps? Now OpenCL? AFAIK, at least 197.x nVIDIA driver needed. But, my machines need to stay with 190.38 which give the best performance @ S@h/stock CUDA23 app. I tested one MW@h WU with the new OpenCL app - immediately error. But, why got my machine with 190.38 the OpenCL app? It's not possible (via server) to send out the OpenCL app only to hosts with at least 197.x nVIDIA driver? If there are a lot of < 197.x driver hosts out there, wasted project server performance. DL/errors, DL/errors and DL/errors.. It's possible via app_info.xml to use the old (IIRC 0.24 CUDA23) app? Or this app don't work with the new WUs? BTW. In past I saw the german translation of this site. Since a few months only english. It's a mistake or wanted?
48) Message boards : Number crunching : GTX 480 (Message 43476) Posted 4 Nov 2010 by Sutaru Tsureku Post: Number crunching : 2 x GTX470 worked with milkyway 0.24 (cuda23)
49) Message boards : Cafe MilkyWay : Milkyway chit chat - CLOSED (Message 43473) Posted 4 Nov 2010 by Sutaru Tsureku Post: 876 messages, now 877 messages ;-) in a thread.. I guess the biggest thread.. Maybe time for a new? ;-) Hi MW@h community! What's up? :-) When the threads near 1000 typically they are closed. Actually I tend to close threads before 1000 posts. I have written Esme to ask her to open a new version. Wow.. 1,000. messages?? At S@h +/- 200 messages and a new thread.. Think also to dial-up user.. ;-) BTW. I don't know where to write this.. My account is now in english. To yesterday it was in german. Maybe a DB mistake?
50) Message boards : Cafe MilkyWay : Milkyway chit chat - CLOSED (Message 43472) Posted 4 Nov 2010 by Sutaru Tsureku Post: YouÂ´ve got a nice RAC Moon. Hi to Julie and Sutaru as well. Hi Mike, nice to see you also here.
51) Message boards : Number crunching : Aaargh! Server out of new work! (Message 43462) Posted 4 Nov 2010 by Sutaru Tsureku Post: We're working on it. -Matthew Thanks for info!
52) Message boards : Cafe MilkyWay : Milkyway chit chat - CLOSED (Message 43424) Posted 2 Nov 2010 by Sutaru Tsureku Post: 876 messages, now 877 messages ;-) in a thread.. I guess the biggest thread.. Maybe time for a new? ;-) Hi MW@h community! What's up? :-)
53) Message boards : News : Slow workunits solved (Message 43423) Posted 2 Nov 2010 by Sutaru Tsureku Post: Just curious.. Why have MW@h a SSE2 CPU app, if BOINC DL autom. only the app without the SSE2 extension? This is just terrible. There's no legitimate reason for it other than the BOINC scheduler being dumb. The non-SSE2 one is intended for the small percentage of people left without it; the SSE2 one should be considered the default. I'll try to work around this. Thanks. Only for the people with knowledge about app_info.xml file and where to DL manually the SSE2 app? app_info.xml is also a pretty unusable system. Somebody should really replace everything managing versions on the client and server. It shouldn't require special knowledge, manually downloading files or manually editing XML, and it should be considerably more flexible than it is now. It doesn't really handle updates, and BOINC just sort of breaks whenever there's an error in the file. But the app_info.xml file is (to now) the only way for us, to install opt. apps. ;-)
54) Message boards : News : Slow workunits solved (Message 43422) Posted 2 Nov 2010 by Sutaru Tsureku Post: I got info, that the old opt. 0.19 CPU app work well with the new ('milkyway') WUs (the last opt. 0.21 not). It would be O.K., to use this old opt. 0.19 CPU app? But, where we could DL this old opt. CPU apps? Maybe someone could 'keep ready' the old opt. apps somewhere for DL? BTW. Gipsel, you are here? When we could get new opt. CPU (milkyway + -nbody) apps? :-)
55) Message boards : Number crunching : CPU + GPU simultaneously? (Message 43421) Posted 2 Nov 2010 by Sutaru Tsureku Post: Hi, the app_info.xml files are not the prob.. ;-) My BOINC get CPU WUs only manually (after changing of the prefs to only CPU). But not automatically simultaneously to the GPU WUs (CPU + GPU in the prefs).
56) Message boards : Number crunching : CPU + GPU simultaneously? (Message 43418) Posted 2 Nov 2010 by Sutaru Tsureku Post: Hello community! Is here someone which have always automatically enough CPU + GPU WUs in BOINC for 24/7 (if the server are available ;-)? Or BOINC have also times, that no CPU or GPU WUs in BOINC? If both enabled in the prefs, my BOINC get only GPU WUs. I need to disable GPU in the prefs, DL a few CPU WUs and enable again GPU. Thanks! EDIT: I think it's not important, but you have an app_info.xml file or not for MW@h?
57) Message boards : Cafe MilkyWay : Definately not Seti....... (Message 43417) Posted 2 Nov 2010 by Sutaru Tsureku Post: The boards are dead from the lack of response to problems and questions over the last year. I am well aware of the reasons........ One of which is my lack of presence. (...) What happened over the last year?
58) Message boards : News : Slow workunits solved (Message 43416) Posted 2 Nov 2010 by Sutaru Tsureku Post: Just curious.. Why have MW@h a SSE2 CPU app, if BOINC DL autom. only the app without the SSE2 extension? Only for the people with knowledge about app_info.xml file and where to DL manually the SSE2 app?
59) Message boards : News : Slow workunits solved (Message 43397) Posted 1 Nov 2010 by Sutaru Tsureku Post: I enabled CPU in the prefs and got the 0.44 app [EDIT: (Win 32bit), 140 KB]. But why not the SSE2 app? BOINC should know that my E7600 can up to SSE4.1 . The result - immediately an error: resultid=234172796 <core_client_version>6.10.58</core_client_version> <![CDATA[ <message> - exit code -1073741515 (0xc0000135) </message> ]]>
60) Message boards : News : a fix for the output file issue (Message 43396) Posted 1 Nov 2010 by Sutaru Tsureku Post: @ admins Please let us know, if it will be possible in future, that MW@h have a separate CPU and GPU WU limit in progress. Thanks! (Like I mentioned it in the upper messages) I read about GPU- and CPU- only user, they have no probs.. ;-) To now, I didn't saw someone with CPU + GPU simultaneously and it work or not. For me, it don't work well autom. simultaneously. If CPU + GPU enabled, only GPU WUs in BOINC.

Previous 20 · Next 20