Changes between Version 5 and Version 6 of WorkShop07/BoincGrid


Ignore:
Timestamp:
Oct 4, 2007, 4:31:25 PM (17 years ago)
Author:
Jack
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • WorkShop07/BoincGrid

    v5 v6  
    1  - Why should BOINC use grids
     1 == Why should BOINC use grids ==
    22    - Resources in general more secure and owners trusted
    33       - Can be used for result verification
    … …  
    1111    - Leverage existing grid software
    1212       - Job submission often simpler with web portals
    13  - Why should grids use BOINC
     13    - Single Scheduling Environment for both High Performance Computing (HPC) resources [Grids] and Volunteer Resources
     14 == Why should grids use BOINC ==
    1415    - Order of magnitude more computing power and storage at fraction of the cost
    1516    - Many grid jobs are already task parallel,
    … …  
    1920          - Concept of an individual user or job (and access rights) in BOINC
    2021          - Credit accounting for these jobs
    21 
    22 == Benefit ==
    23  - Single Scheduling Environment for both High Performance Computing (HPC) resources [Grids] and Volunteer Resources
    24  - Validation of work units -- Due the homogenous nature of HPC/Grids it is thought that they are more reliable than volunteer resources; however even in these environments data corrupt occurs (system failure, administrative outages, etc)
    25 
    26 == Problems ==
    27 There are some pit falls that have been identified by uses BOINC on some Grid computing systems. Most of the problems identified in this session dealt with HPC/Grid Submission Systems and efficient use of Grid resources (allotted grid computing hours). 
    28  - Problem 1: Scheduled Grid client runs when server has no work
     22       - There are some pit falls that have been identified by uses BOINC on some Grid computing systems. Most of the problems identified in this session dealt with HPC/Grid Submission Systems and efficient use of Grid resources (allotted grid computing hours). 
     23 -- Problem 1: Scheduled Grid client runs when server has no work
    2924The client would be idle burning time from the users allotted computer hours.
    30  - Problem 2: Grid Scheduler kills jobs after time expires
     25 -- Problem 2: Grid Scheduler kills jobs after time expires
    3126Even with check pointing data processed on the last WU would be lost. The workspace would be scratched.
    3227