Posts by Werinbert

1) Questions and Answers : Windows : Nvidia driver 461.09 causes wu's to stall/run indefinitely, 460.79 works fine (Message 70477) Posted 30 Jan 2021 by Werinbert Post: I converted one of my computers from Linux to Win 10 a couple of days ago. At the time I installed the 461.09 drivers. My GPU has been happily crunching MW tasks since. The drivers were loaded after installing windows and I have not let windows update anything, so I suspect it was some windows update causing the problem not the Nvidia drivers.
2) Message boards : Number crunching : Finally getting new tasks only seconds after running out. May not be worth the hassle. (Message 69706) Posted 14 Apr 2020 by Werinbert Post: I am running Milkyway@home Separation on my GPU.... The "NVIDIA GPU task request deferred for 00:0x:xx" in conjunction with "NVIDIA GPU task request deferral interval for 00:10:00" is getting painfully problematic as it prevents me from downloading new work. Whenever I return tasks to the server this deferral gets reset and my computer gets no new tasks. On my GTX 1660 Ti i have gone to running four tasks simultaneously to increase the time it takes to send back to the server, now at around 12 minutes, still this is not enough as too many results are still returned and the deferral is yet again postponed. I have even tried settings to grab a larger number of tasks, but instead of helping it ended up messing up my other projects. I don't want to download any special version of boinc as this is not my primary project. Maybe I should be running more than four tasks? ...although the four are already causing havoc with cpu loads... In any case MW's failure to keep my computer continually loaded is a boon to my other projects which are more than happy to fill a 10 minute gap with hours of work.
3) Message boards : News : N-Body 1.40 (Message 60825) Posted 27 Jan 2014 by Werinbert Post: Jake, when are we going to get the non-mt WU? Long mt-WUs tax the poor little Boinc brain....
4) Message boards : News : N-Body 1.38 (Message 60729) Posted 13 Jan 2014 by Werinbert Post: We noticed this was a problem. I am of the opinion that there is no inherent advantage to running MT tasks and plan to release only non-MT versions for the next n-body release. As alluded to in the previous posts, I have found another problem using MT apps. As TJ said, they want to use all cores. In my case, I am still using all cores, however, I am running another WU that is running in high priority (RNA World). In this situation the MT WU is not run and sits idle. Idle WUs, none the less, are figured into the work buffer computation making Boinc think that I have lots of WUs waiting to run. Consequently, the other threads start to run dry. Because of this problem, I am now considering all MT apps (for any project) to be off-limits. Is it possible to separate the MT from non-MT n-Body WUs and add as a project preference? I also wonder if it is possible to create a preference setting to limit the number of cpus used by MT apps. ...I should make a request on the Boinc forms...
5) Message boards : Number crunching : Poor likelihood????? (Message 60659) Posted 27 Dec 2013 by Werinbert Post: stderr output for n-body simulations... A lot of my WUs are returning the following results: Poor likelihood. Returning worst case. <search_likelihood>-9999999.900000000400000</search_likelihood> Is this within the realm of reason and I should ignore it or is this an indicator of something not right with this current batch?
6) Message boards : News : New MilkyWay Separation Modified Fit Runs (Message 60358) Posted 11 Nov 2013 by Werinbert Post: I just started a run of MW Separation (Modified fit) for cpus. I am still seeing the problem of varying run times but granting the same credits. The _bpl_ tasks taking nearly twice as long as the other tasks (15.6ksec vs 8.7ksec).
7) Message boards : News : N-Body 1.38 (Message 60355) Posted 11 Nov 2013 by Werinbert Post: With MT or without MT... Is there any project advantage to running the MT app over the non-MT app? I have been running both for a while now and for the most part they return about the same cr/effort across my computers. If anything, the non-MT actually has a better cr/effort ratio. MT on the other hand plays "less nice" with other WU's as they demand all threads and kick the other WUs into the "waiting to run" state. Thankfully the MT WUs are quite fast and only a minor inconvenience. [Try Yafu and their 12+hr mt WUs messing up Boinc scheduling big time.] So I am wondering, if there is no project advantage to MT why not just go the non-MT route? Or create a preference allowing one or the other or both?