DistOS-2011W Public Goods: Difference between revisions

From Soma-notes
Lmundt (talk | contribs)
Aschoenr (talk | contribs)
No edit summary
Line 29: Line 29:


One example paper [http://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.40.8364&rep=rep1&type=pdf Improving Web Server Performance by Caching Dynamic Data]
One example paper [http://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.40.8364&rep=rep1&type=pdf Improving Web Server Performance by Caching Dynamic Data]
==Tuesday March 8==
Currently our idea of public goods consists of:
*Distributed file storage
**[http://www.usenix.org/events/osdi06/tech/weil.html Ceph] seems to be an ideal candidate for this
*Distributed Computation
**To avoid a [http://en.wikipedia.org/wiki/Tragedy_of_the_commons tragedy of the commons] situation with both the storage and computation resources, only predetermined, agreed upon computation will take place which has a net benefit to everyone participating. This computation is based on the data stored at each node and the results (metadata) will be stored locally. This computation can be done by using idle cycles, much like [http://en.wikipedia.org/wiki/Berkeley_Open_Infrastructure_for_Network_Computing BOINC] projects.
**Must allow for querying of metadata to allow users to effectively search processed data.
*Administration
**Main issue: how are services agreed upon? Once a service is implemented (ie. image store) distributing it getting it running isn't a major issue.

Revision as of 15:15, 8 March 2011

Members

  • Lester Mundt - lmundt at connect.carleton.ca
  • Fahim Rahman - frahman at connect.carleton.ca
  • Andrew Schoenrock - aschoenr at scs.carleton.ca

Tuesday March 1

Key components:

  • Distributed File System
    • Can use something previously presented in class
  • Distributed computation
  • Administration
    • How much does a person need to contribute to the system?
    • How will users submit (small) services they would like to have run?
    • How can very large services be established (from idea to implementation)?

Todo for March 8th:

    • Find papers on distributed computation and administration

Thursday March 3

  • Seek out papers on specific topic of distributed web cache.
  • Discussed two other interesting public goods or services.
    • Image registry
    • DNA registry - found one article that suggests uncompressed the human genome is between 1.5 and 30 terrabytes but more efficient formats exist that bring it down to 1.5GB
http://www.genetic-future.com/2008/06/how-much-data-is-human-genome-it.html 


One example paper Improving Web Server Performance by Caching Dynamic Data

Tuesday March 8

Currently our idea of public goods consists of:

  • Distributed file storage
    • Ceph seems to be an ideal candidate for this
  • Distributed Computation
    • To avoid a tragedy of the commons situation with both the storage and computation resources, only predetermined, agreed upon computation will take place which has a net benefit to everyone participating. This computation is based on the data stored at each node and the results (metadata) will be stored locally. This computation can be done by using idle cycles, much like BOINC projects.
    • Must allow for querying of metadata to allow users to effectively search processed data.
  • Administration
    • Main issue: how are services agreed upon? Once a service is implemented (ie. image store) distributing it getting it running isn't a major issue.