1 / 10

Distributed Filesystems (part 1)

Distributed Filesystems (part 1). CPS210 Spring 2006. Papers. Scale and Performance in a Distributed File System John Howard + Satya. Process of building AFS. Example of the ideal systems design cycle (rare to actually see, especially 2.) Build a prototype Get people to use it (hard)

jamesgrimm
Télécharger la présentation

Distributed Filesystems (part 1)

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Distributed Filesystems (part 1) CPS210 Spring 2006

  2. Papers • Scale and Performance in a Distributed File System • John Howard + Satya

  3. Process of building AFS • Example of the ideal systems design cycle • (rare to actually see, especially 2.) • Build a prototype • Get people to use it (hard) • See what doesn’t work • Traces and benchmarks • Fix what doesn’t work • Goto 1.

  4. Venus structure (first read) file cache Vice F App Venus stat cache F F stat F open read Kernel Venus kernel module

  5. Venus structure (write) file cache Vice F’ F’ F App Venus F’ stat cache F’ F F stat F’ stat F close write Kernel Venus kernel module

  6. Venus structure (second read) file cache Vice F’ F’ App Venus stat cache F F’ stat F’ open read Kernel Venus kernel module

  7. Venus-vice interactions 2 reads for every write

  8. Andrew benchmark • Start with read-only source tree • Outside of measured file system! • Phases • MakeDir • Copy • ScanDir • ReadAll • Make • What are the limitations of this?

  9. Benchmark results with load • Clearly, Vice is not scaling well • Cache consistency protocol really isn’t

  10. Callbacks • Servers now invalidate caches • Called “breaking a callback” • Why is this better? • Client no longer polls for invaldations • Sharing is extremely rare • Most polls did not invalidate the cache • What state does the server need?

More Related