Message boards :
Number crunching :
Milkyway@home N-Body Simulation, limit to just 1 thread and slow CPUs ?
Message board moderation
Author | Message |
---|---|
Send message Joined: 30 Apr 09 Posts: 101 Credit: 29,874,293 RAC: 0 |
Hello :) I have just a slow CPU : Intel(R) Celeron(R) CPU J1900 @ 1.99GHz [Family 6 Model 55 Stepping 8] (4 real Cores) I would like to limit the N-Body Simulation app to just 1 CPU thread (with app_config.xml file). I'm unsure if the WUs will finish during the 12 days deadline. A Milkyway@home Separation WU lasts around 6 hours - for to compare. Just crunching, no other things at the same time. I work and play games during crunching, so the calculations time of the WUs increase... Maybe you have also a slow CPU and you limit the N-Body Simulation app just to 1 thread? I could limit the app to just 1 thread - what you think? Thanks :) |
Send message Joined: 8 May 09 Posts: 3339 Credit: 524,010,781 RAC: 0 |
Hello :) I don't run those at all but an app_config.xml file might fix it for you |
Send message Joined: 30 Apr 09 Posts: 101 Credit: 29,874,293 RAC: 0 |
Yes, an app_config.xml file could do this... ;) But I'm unsure if the/my slow CPU can finish N-Body Simulation WUs (they vary a lot) during the 12 days, just with 1 thread. ;) I would like to know experiences from others which have similar slow CPUs - if it's possible to finish N-Body Simulation WUs before deadline with just 1 thread... I wouldn't like to let it run just for test, it would be waste of CPU time if it won't finish before deadline... ;) Thanks :) |
©2024 Astroinformatics Group