DOC PREVIEW
Berkeley COMPSCI C267 - Designing Middleware for Volunteer Computing

This preview shows page 1-2-23-24 out of 24 pages.

Save
View full document
View full document
Premium Document
Do you want full access? Go Premium and unlock all 24 pages.
Access to all documents
Download any document
Ad free experience
View full document
Premium Document
Do you want full access? Go Premium and unlock all 24 pages.
Access to all documents
Download any document
Ad free experience
View full document
Premium Document
Do you want full access? Go Premium and unlock all 24 pages.
Access to all documents
Download any document
Ad free experience
View full document
Premium Document
Do you want full access? Go Premium and unlock all 24 pages.
Access to all documents
Download any document
Ad free experience
Premium Document
Do you want full access? Go Premium and unlock all 24 pages.
Access to all documents
Download any document
Ad free experience

Unformatted text preview:

Slide 1Slide 2Slide 3Slide 4Slide 5Slide 6Slide 7Slide 8Slide 9Slide 10Slide 11Slide 12Slide 13Slide 14Slide 15Slide 16Slide 17Slide 18Slide 19Slide 20Slide 21Slide 22Slide 23Slide 24David P. AndersonSpace Sciences LaboratoryUniversity of California – [email protected] Middleware for Volunteer ComputingWhy volunteer computing?●2006: 1 billion PCs, 55% privately owned●If 100M people participate:–100 PetaFLOPs, 1 Exabyte (10^18) storage●Consumer products drive technology–GPUs (NVIDIA, Sony Cell)your computersacademicbusinesshome PCsVolunteer computing history95 96 97 98 99 00 01 02 03 04 05 06GIMPS, distributed.netSETI@home, folding@homecommercial projectsclimateprediction.netBOINCEinstein@homeRosetta@homePredictor@[email protected] computing paradigmsGrid computingSupercomputersVolunteer computingCluster computingControlBang/buckleastleastmostmostBOINCSETI physicsClimatebiomedicalJoeAliceJensvolunteersprojectsParticipation in >1 project●Better short-term resource utilization–communicate/compute in parallel–match applications to resources●Better long-term resource utilization– project A works while project B thinksprojectcomputingneedsthinkworkthinkworktimeServer performanceHow many clients can a project support?Task server architectureMySQLTransitionerSchedulerFeederFile deleter DB purgerAssimilatorValidatorWork creatorShared memclientsServer load (CPU)Create Send Validate Assimilate File delete DB purge050100150200250300350CPU seconds per 100,000 tasksApplicationMySQLServer load (disk I/O)Create Send Validate Assimilate File delete DB purge050100150200250300350400Disk I/O (MB) per 100,000 tasksServer limits●Single server (2X Xeon, 100 Mbps disk)–8.8 million tasks/day–4.4 PetaFLOPS (if 12 hrs on 1 GFLOPS CPU)–CPU is bottleneck (2.5% disk utilization)–8.2 Mbps network (if 10K request/reply)●Multiple servers (1 MySQL, 2 for others)–23.6 million tasks/day–MySQL CPU is bottleneck–21.9 Mbps networkCreditCredit displayCredit system goals●Retain participants–fair between users, across projects–understandable–cheat-resistant●Maximize utility to projects–hardware upgrades–assignment of projects to computersCredit system●Computation credit–benchmark-based–application benchmarks–application operation counting–cheat-resistance: redundancy●Other resources–network, disk storage, RAM●Other behaviors–recruitment–other participationBenchmarks not whole storyLimits of Volunteer Computing●How much processing/disk/RAM is out there?●Combinations of resources●Data from 330,000 SETI@home participantsOperating system Number of hosts GFLOPS per host GFLOPS total Windows total 292,688 1.676 490,545 XP 229,555 1.739 399,196 2000 42,830 1.310 56,107 2003 10,367 2.690 27,887 98 6,591 0.680 4,482 Millennium 1,973 0.789 1,557 NT 1,249 0.754 942 Longhorn 86 2.054 177 95 37 0.453 17 Linux 21,042 1.148 24,156 Darwin 15,830 1.150 18,205 SunOS 1,091 0.852 930 Others 1,134 1.364 1,547 Total 331,785 1.613 535,169Goals of BOINC●> 100 projects, some churn●Handle big data better–BitTorrent integration–Use GPUs and other resources–DAGs●Participation–10-100 million–multiple projects per


View Full Document

Berkeley COMPSCI C267 - Designing Middleware for Volunteer Computing

Documents in this Course
Lecture 4

Lecture 4

52 pages

Split-C

Split-C

5 pages

Lecture 5

Lecture 5

40 pages

Load more
Download Designing Middleware for Volunteer Computing
Our administrator received your request to download this document. We will send you the file to your email shortly.
Loading Unlocking...
Login

Join to view Designing Middleware for Volunteer Computing and access 3M+ class-specific study document.

or
We will never post anything without your permission.
Don't have an account?
Sign Up

Join to view Designing Middleware for Volunteer Computing 2 2 and access 3M+ class-specific study document.

or

By creating an account you agree to our Privacy Policy and Terms Of Use

Already a member?