BOINC uses all available processing resources; if this is not the case with 6.10.4, send an example message log.
Al Reust wrote: > Sorry for Top Posting... > > When this silly Cuda stuff was started the assumption was that Cuda would > fit inside the current scheduler so that if 4 CPU's were identified it > would "fit" inside the 4 CPU Scheme. In Seti there is a silly user that has > 4 - 295's that complains that the scheduler will not give work for the 4 > 295's and is limited to the 4 cores that is identified by the BOINC Client. > > So to say that while developing a New Plan class on a flawed system is okay > and not worth the time or resources. Someone need to rethink for a moment. > Both the Scheduler and the Client do not properly deal with the existing > Cuda instance. Then Multithreading is already underway in various projects. > Various issues have been identified here, what is the scheduler supposed to > do for those instances. A Blade Server with 48 CPU's or one of Nvidia's > Tesla S1070. Something has to get a bit smarter. We are no longer dealing > with a single computer. _______________________________________________ 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.
