| 2 |
Distributed Shared Memory |
1% |
- Groups 1 and 2:
- Compare Ivy and Dash in terms of considtency models, shared-data
granularity, HW/SW implementation, false sharing, and
implementation. What types of applications can Ivy and Dash benefit
respectively?
- Solve slide p24's non-turn-in exercise 1.
- Groups 3 and 4:
- Compare distributed shared memory and message passing (such as
MPI) in terms of programmability and performance. Discuss about their
pros and cons using two types of applications: computer graphics such
as 3D ray tracing and spatial simulation such as molecular dynamics.
- Solve slide p24's non-turn-in exercise 2.
|
| 4 |
Fault Tolerane |
1% |
- Groups 1 and 2:
- Could the gossip architecture be used for a distributed computer
game as described below? The players move figures around a common
scene. The state of the game is replicated at the players'
workstations and at a server, which contains services controlling the
game overall, such as collision detection. Updates are multicast to
all replicas. (Textbook Q18.11)
- Suppose that a user wants to use Gossip for grid-computing
middleware where s/he runs a massively parallel application with a
large number of remote computers. Each process running at a different
computer has a postive sequential identifier, periodically takes an
execution snapshot, monitors its logical neighbor with a one-larger
identifier, and resumes this neighbor at a new computer if it has
crashed for some reason. Discuss how Gossip faciliates this fault
tolerance in grid computing.
- Groups 3 and 4:
- The quorum-based replication protocol can address network
partition problems. Why didn't Code use this protocol? Explain the
reason.
- Suppose that a user wants to use Coda for grid-computing
middleware where s/he runs a massively parallel application with a
large number of remote (network-detachable) computers. Each process
running at a different computer has a postive sequential identifier,
periodically takes an execution snapshot, monitors its logical
neighbor with a one-larger identifier, and resumes this neighbor at a
new computer if it has crashed for some reason. Discuss how Coda
faciliates this fault tolerance in grid computing.
|
| 5 |
Grid Computing |
1% |
- Groups 1 and 2:
Summarize how Condor, Legion, NetSolve, and Globus facilitate the following two features:
- Discoveries of remote computing resources
- Job deployment to remote computers
- Groups 3 and 4:
Summarize how Condor, Legion, NetSolve, and Globus facilitate the following two features:
- Fault tolerance, (i.e., a job resumption at a new site)
- I/O, (i.e., rerouting files and standard I/O data to remote jobs)
For these discussions, you have to survey about these grid-computing
middleware systems.
NetSolve
- http://icl.cs.utk.edu/netsolve/
- Henri Casanova, Jack Dongarra, Chris Johnson, and Michelle Miller,
"Section 7.3: Case Study: NetSolve", In Ian Foster and Carl Kesselman,
editors, The Grid: Blueprint for a New Computing Infrastracture,
Morgan Kaufmann Publishers, July 1998, pages 171-175 (available from
the instructor)
Legion
- http://legion.virginia.edu/
- Dennies Gannon and Andrew Gimshaw, "Section 9.4: The Legion Grid Architecture", In Ian Foster and Carl Kesselman, editors, The Grid:
Blueprint for a New Computing Infrastracture, Morgan Kaufmann
Publishers, July 1998, pages 222-227 (available from the instructor)
Condor
- http://www.cs.wisc.edu/condor
-
Douglas Thain, Todd Tannenbaum, and Miron Livny,
"Condor and the Grid",
in Fran Berman, Anthony J.G. Hey, Geoffrey Fox, editors, Grid Computing:
Making The Global Infrastructure a Reality, John Wiley, 2003. ISBN: 0-470-85319-0
Globus
- http://www.globus.org/
- Ian Foster and Carl Kesselman, "Chapter 11: The Globus Toolkit",
In Ian Foster and Carl Kesselman, editors, The Grid: Blueprint for a
New Computing Infrastracture, Morgan Kaufmann Publishers, July 1998,
pages 222-227 (available from the instructor)
|