The BOINC API option affects only the main thread. Any threads created by the app run at priority THREAD_PRIORITY_NORMAL by default; see http://msdn.microsoft.com/en-us/library/ms682453%28VS.85%29.aspx
It's up to the app to set the priority of the threads it creates (either to THREAD_PRIORITY_IDLE, or better yet to whatever the priority of the main thread is). -- David Richard Haselgrove wrote: > I happened to come across the AQUA application using priority 4 for threads > 2,3,4: > > http://img707.imageshack.us/img707/7710/aquathreads.png > > (The base application runs at priority 1, as one would expect). > > I'm assuming the 4 comes from IDLE_PRIORITY_CLASS : THREAD_PRIORITY_NORMAL > > I asked the AQUA admins if they had deliberately set priority 4, and their > response was "Upon looking into it, it looks like there's some > boinc_init_options thing in the main app's code that might have been to fix > that bizarre default." - which I take to mean 'no'. > > As you can see from the screenshot, the secondary etc. threads run as > VCOMP90.DLL: presumably there is no need for such a DLL to run boinc_init > API code, and hence get reset to THREAD_PRIORITY_IDLE. Is there any way for > BOINC to set thread priorities for secondary threads, or is it a matter for > an APB documentation update to developers of MT apps? > > Reference: http://aqua.dwavesys.com/forum_thread.php?id=389 > > > _______________________________________________ > boinc_dev mailing list > [email protected] > http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev > To unsubscribe, visit the above URL and > (near bottom of page) enter your email address. _______________________________________________ boinc_dev mailing list [email protected] http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev To unsubscribe, visit the above URL and (near bottom of page) enter your email address.
