Presentation information: Difference between revisions

From ReddNet
Jump to navigation Jump to search
No edit summary
Line 4: Line 4:
= Development timeline =
= Development timeline =
* Existing protocol documentation (real soon)
* Existing protocol documentation (real soon)
* Add web page for ACCRE IBP depot software releases(real soon)
* Add web page for ACCRE IBP depot software and tools releases(real soon)
** ACCRE IBP Depot
** ibp_perf - IBP server benchmarking tool. Benchmarks:
*** allocation creates / sec
*** allocation removals / sec
*** Upload performance (MB/s)
*** Download performance (MB/s)
*** Mixed upload/download performance. upload/download ratio is a user controlled parameter (MB/s)
** ibp_sperf - Benchmarks FIFO performance along a chain of depots.  Provides one way transfer rate.
** It's probably more suited to binary distribution since their is no autotool support yet.
** It's probably more suited to binary distribution since their is no autotool support yet.
* Re-implement C IBP client (4/1/08 - it's a longtime but I have to work around ACCRE downtime in mid-march)
* Re-implement C IBP client (4/1/08 - it's a longtime but I have to work around ACCRE downtime in mid-march)
Line 10: Line 18:
** This will be a draft implementation which will probably be thrown out
** This will be a draft implementation which will probably be thrown out
** How fast this gets done is really dependent on coming up with the minimal set needed for the directory+data services api and protocol.  Also depends on Larry's time getting similar support into L-Store.  Micah/Chris, what about LoDN supporting it also?
** How fast this gets done is really dependent on coming up with the minimal set needed for the directory+data services api and protocol.  Also depends on Larry's time getting similar support into L-Store.  Micah/Chris, what about LoDN supporting it also?
 
** Minimal functionality: open, close, fread
* Create Asynchronous IBP client API - no protocol change, just add client side optimizations.
* Create Asynchronous IBP client API - no protocol change, just add client side optimizations.
* Minimal StdIO/FUSE module which supports Async IBP for improved performance
* Minimal StdIO/FUSE module which supports Async IBP for improved performance

Revision as of 18:33, 24 January 2008

Proposed changes

Follow link for details

Development timeline

  • Existing protocol documentation (real soon)
  • Add web page for ACCRE IBP depot software and tools releases(real soon)
    • ACCRE IBP Depot
    • ibp_perf - IBP server benchmarking tool. Benchmarks:
      • allocation creates / sec
      • allocation removals / sec
      • Upload performance (MB/s)
      • Download performance (MB/s)
      • Mixed upload/download performance. upload/download ratio is a user controlled parameter (MB/s)
    • ibp_sperf - Benchmarks FIFO performance along a chain of depots. Provides one way transfer rate.
    • It's probably more suited to binary distribution since their is no autotool support yet.
  • Re-implement C IBP client (4/1/08 - it's a longtime but I have to work around ACCRE downtime in mid-march)
  • 1st draft: Create minimal Linux/Mac StdIO/FUSE module using directory and data service API and protocol (6/1/08)
    • This will be a draft implementation which will probably be thrown out
    • How fast this gets done is really dependent on coming up with the minimal set needed for the directory+data services api and protocol. Also depends on Larry's time getting similar support into L-Store. Micah/Chris, what about LoDN supporting it also?
    • Minimal functionality: open, close, fread
  • Create Asynchronous IBP client API - no protocol change, just add client side optimizations.
  • Minimal StdIO/FUSE module which supports Async IBP for improved performance