Changes between Version 25 and Version 26 of Performance


Ignore:
Timestamp:
2008-01-30T19:04:18Z (17 years ago)
Author:
warner
Comment:

update SSK latency/creation-time graph links

Legend:

Unmodified
Added
Removed
Modified
  • Performance

    v25 v26  
    6262[/tahoe-figleaf-graph/hanford.allmydata.com-tahoe_speedstats_rate.html rate graph] show these Ax+B numbers for a node in colo and a node behind a DSL line.
    6363
    64 The [/tahoe-figleaf-graph/hanford.allmydata.com-tahoe_speedstats_delay_SSK.html mutable-file delay graph] shows the "B" per-file latency number
    65 for mutable (aka "SSK") files. In the 0.7.0 release, this is dominated by the RSA keypair generation necessary to create each new mutable file.
    66 
    6764The
    6865[/tahoe-figleaf-graph/hanford.allmydata.com-tahoe_speedstats_delay_rtt.html delay*RTT graph] shows this per-file delay as a multiple of the average round-trip
     
    7168per-file delay in units of RTT helps to compare the observed performance
    7269against the predicted value.
     70
     71=== Mutable Files ===
     72
     73Tahoe's mutable files (sometimes known as "SSK" files) are encoded
     74differently than the immutable ones (aka "CHK" files). Creating these mutable
     75file slots currently (in release 0.7.0) requires an RSA keypair generation.
     76[http://allmydata.org/tahoe-figleaf-graph/hanford.allmydata.com-tahoe_speedstats_SSK_creation.html This graph]
     77tracks the amount of time it takes to perform
     78this step.
     79
     80There is also per-file overhead for upload and download, just like with CHK
     81files, mostly involving the queries to find out which servers are holding
     82which versions of the file. The
     83[/tahoe-figleaf-graph/hanford.allmydata.com-tahoe_speedstats_delay_SSK.html mutable-file delay graph]
     84shows this "B" per-file latency value.
     85
     86The "A" transfer rate for SSK files is also tracked. TODO: add a link to the
     87graph.
    7388
    7489=== Roundtrips ===