Changes between Version 15 and Version 16 of BoincPlatforms


Ignore:
Timestamp:
Feb 25, 2008, 10:17:11 AM (16 years ago)
Author:
Nicolas
Comment:

Anchors and uncommented section about alt platform

Legend:

Unmodified
Added
Removed
Modified
  • BoincPlatforms

    v15 v16  
    11= Platforms =
    22       
    3 
    43The computers available to a volunteer computing project have a wide range of operating systems and hardware architectures. For example, they may run many versions of Windows (95, 98, ME, 2000, XP) on many processors variants (486, Pentium, AMD). Hosts may have multiple processors and/or graphics coprocessors.
    54
     
    4342A platform name is compiled into the BOINC client. The client reports its platform to the scheduling server, and the scheduling server sends work to a host only if there is an application version for the same platform.
    4443
    45 {{{
    46 #!comment
    47 Since version X, the BOINC client supports alternate platforms. For example, a Mac/Intel host is able to run Mac/PPC applications in emulation mode. Mac/Intel clients will ask for work specifying Mac/Intel as main platform and Mac/PPC as alternate platform. If your project doesn't have a Mac/Intel application, such hosts will still be able to participate in your project, using the PPC application.
    48 }}}
     44Since version 5.9.6, the BOINC client supports alternate platforms. For example, a Mac/Intel host is able to run Mac/PPC applications in emulation mode. Mac/Intel clients will ask for work specifying Mac/Intel as main platform and Mac/PPC as alternate platform. If your project doesn't have a Mac/Intel application, such hosts will still be able to participate in your project, using the PPC application.
    4945
    50 == Application optimization for specific architectures ==
     46== Application optimization for specific architectures == #optimization
    5147
    5248BOINC allows applications to exploit specific architectures, but places the burden of recognizing the architecture on the application. In other words, if you want to make a version of your application that can use the AMD 3DNow instruction set, don't create a new '''windows_amd_3dnow''' platform. Instead, make a version for the '''windows_intelx86''' platform that recognizes when it's running on a 3DNow machine, and branches to the appropriate code.
     
    5450This excludes the combinatorial explosion of versions and architectures from the internals of BOINC.
    5551
    56 == Web-site statistics breakdown by architecture ==
     52== Web-site statistics breakdown by architecture == #arch-stats
    5753
    5854BOINC collects architecture details about each completed result to allow detailed statistical breakdowns.
     
    6965This makes it possible, for example, to report average or total performance statistics for 3DNow hosts contrasted with other Intel-compatible hosts.
    7066
    71 == Tools ==
     67== Tools == #tools
    7268
    7369Platforms are maintained in the '''platform''' table in the BOINC DB, and can be created using the [XaddTool xadd] utility.