Posts by computezrmle

1) Message boards : Number crunching : N-Body tune initial replication value (Message 76109) Posted 1 Jul 2023 by computezrmle Post: I did not yet find a single valid N-Body WU without at least 2 results. Could anybody post a link to an example with only 1 result? From my 8-core i7 (tweaked to 2 cores) https://milkyway.cs.rpi.edu/milkyway/show_host_detail.php?hostid=994185: Application details for host 994185 Milkyway@home N-Body Simulation 1.82 x86_64-pc-linux-gnu (mt) Number of tasks completed 23 Max tasks per day 20023 Number of tasks today 2 Consecutive valid tasks 23 Average processing rate 1.72 GFLOPS Average turnaround time 0.29 days It looks like the "Max tasks per day" value had been optimized for Separation but is now far too high for N-Body.
2) Message boards : Number crunching : N-Body tune initial replication value (Message 76107) Posted 1 Jul 2023 by computezrmle Post: N-Body simulations seem to require at least 2 results being returned to get validated. Most of the WU details I checked show that the initial replication is set to 1 and the 2nd result is not sent out before the 1st result has been reported back. Wouldn't it be more efficient to set the initial replication to "2"? This would allow 2 wingmen to process a WU concurrently.
3) Message boards : News : Nbody WU Flush (Message 73922) Posted 26 Jun 2022 by computezrmle Post: CPU-Z always reports the actual CPU Feel free to use CPU-Z for scientific calculations. ;-) Another option would be that you improve the BOINC code and implement a reliable method like that from CPU-Z. Or ... (many more options...)
4) Message boards : News : Nbody WU Flush (Message 73920) Posted 26 Jun 2022 by computezrmle Post: I didn't reply to your post. (You don't even notice when anybody agrees with you, don't you?) BTW: Peter Hucker of the Scottish Boinc Team wrote: Presumably Boinc is just reporting a range, which is annoying and useless. Don't blame BOINC for this - it just reports what it gets from the computer's BIOS. Hence, blame the BIOS manufacturer. Much better: Don't blame anybody.
5) Message boards : News : Nbody WU Flush (Message 73916) Posted 26 Jun 2022 by computezrmle Post: Hmmm, threads or cores ? From the already given Intel overview just click on the links to the detailed specs. Most CPUs have 4 cores/8 threads and hyper-threading. Only a few don't. Hint: https://ark.intel.com/content/www/us/en/ark/products/52271/intel-xeon-processor-e31230-8m-cache-3-20-ghz.html
6) Message boards : Number crunching : Setting up multiple instances of BOINC in Windows (Message 73784) Posted 3 Jun 2022 by computezrmle Post: The issue is, I get unwanted CPU separation tasks when I run NVIDIA and AMD separation. If all 3 BOINC clients run fine on your box you need to attach CPU and GPU clients to different venues at the MW server. Then set the venue options according to your needs, e.g. switch "use CPU" off for "GPU only" clients if you don't want "CPU separation" tasks.
7) Message boards : Number crunching : Setting up multiple instances of BOINC in Windows (Message 73772) Posted 2 Jun 2022 by computezrmle Post: Sometimes project servers are too "smart" when you attach an additional client from the same box that has already attached a client. They merge both entries. You need to force the server to create a fresh computer ID in it's DB. In most cases it's enough to fake "<ncpus>x</ncpus>" in cc_config.xml. Reload config files and contact the project from both clients. Once you got a fresh host ID for one client you can remove the fake setting. Check the local logs and the project's computer list for the new IDs.
8) Message boards : Number crunching : A plea for more options (Message 73607) Posted 20 May 2022 by computezrmle Post: Without changing the server's source code the project admin would have to split the separation app into - an app for GPUs only - an app for CPUs only Then volunteers could select the apps they want to run per venue at the prefs page: https://milkyway.cs.rpi.edu/milkyway/prefs.php?subset=project