> At the moment, the BOINC client scheduler can't make use of those idle > resources: all cores are released back to BOINC 'en bloc' when the whole > task finishes. Releasing individual cores for re-use by BOINC is probably > a scheduler request too far, but if thread equality levels the playing > field, efficiency overall should improve - the AQUA devs are looking into > it.
I really have big doubts that MT AQUA will increase overall BOINC (even if it will do it for AQUA project itself) performance on host. Firstly, for what reason AQUA wanna use multithreaded app? If I understood correctly what I read on their site some time ago - the main reason - unacceptable long running times for their tasks. If single task will be run on multicore host by MT app and will have at least _some_ level of parralelism, it will be completed faster of course. That is, this aim clearly will be accomplished by MT app. But there is _nothing_ about performance. Actually, very probably overall performance will decrease, even w/o BOINC's too generous CPU resourse allocations for this project. And to get true benefit (in performance sense, not in just single task completion time sense) some benefits from better L2 cache usage required and perfect synching and load balancing between threads of course. _______________________________________________ boinc_dev mailing list boinc_dev@ssl.berkeley.edu http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev To unsubscribe, visit the above URL and (near bottom of page) enter your email address.
