mutable publish: add timing charts to measure RTT #394

Open
opened 2008-04-24 23:20:23 +00:00 by warner · 2 comments
warner commented 2008-04-24 23:20:23 +00:00
Owner

We should examine the mutable-file publish process to try and get small files to do read-modify-write in two RTT. Large files should be three RTT (one to update the servermap, a second to read the data, a third to write the data).

The first step for this will be better status/visualization tools. Servermap update has a little diagram (using the Google Chart API) of how the queries are spaced out. I'd like to:

  • make these charts for all mutable file operations
  • for retrieve, show both the mapupdate queries and the retrieve queries on the same chart
  • for publish, show mapupdate and publish on the same chart
  • (maybe) for modify, show everything on the same chart
  • switch to PIL to get better diagrams and show overlapping queries

I think we may be at 3RTT already, but I'm not sure, and better tools would help me be sure.

We should examine the mutable-file publish process to try and get small files to do read-modify-write in two RTT. Large files should be three RTT (one to update the servermap, a second to read the data, a third to write the data). The first step for this will be better status/visualization tools. Servermap update has a little diagram (using the Google Chart API) of how the queries are spaced out. I'd like to: * make these charts for all mutable file operations * for retrieve, show both the mapupdate queries and the retrieve queries on the same chart * for publish, show mapupdate and publish on the same chart * (maybe) for modify, show everything on the same chart * switch to PIL to get better diagrams and show overlapping queries I think we may be at 3RTT already, but I'm not sure, and better tools would help me be sure.
tahoe-lafs added the
major
task
1.0.0
labels 2008-04-24 23:20:23 +00:00
tahoe-lafs added this to the eventually milestone 2008-04-24 23:20:23 +00:00
warner commented 2008-06-01 20:45:59 +00:00
Author
Owner

I think we're at two RTT for small files, but I still want better diagrams, so I'm changing the title of this ticket.

I think we're at two RTT for small files, but I still want better diagrams, so I'm changing the title of this ticket.
tahoe-lafs modified the milestone from eventually to undecided 2008-06-01 20:45:59 +00:00
tahoe-lafs changed title from mutable: publish should take two RTT to mutable publish: add timing charts to measure RTT 2008-06-01 20:45:59 +00:00
tahoe-lafs added the
code-mutable
label 2009-12-04 05:07:13 +00:00
zooko commented 2010-05-26 14:51:17 +00:00
Author
Owner

It's really bothering me that mutable file upload and download behavior is so finicky, buggy, inefficient, hard to understand, different from immutable file upload and download behavior, etc. So I'm putting a bunch of tickets into the "1.8" Milestone. I am not, however, at this time, volunteering to work on these tickets, so it might be a mistake to put them into the 1.8 Milestone, but I really hope that someone else will volunteer or that I will decide to do it myself. :-)

It's really bothering me that mutable file upload and download behavior is so finicky, buggy, inefficient, hard to understand, different from immutable file upload and download behavior, etc. So I'm putting a bunch of tickets into the "1.8" Milestone. I am not, however, at this time, volunteering to work on these tickets, so it might be a mistake to put them into the 1.8 Milestone, but I really hope that someone else will volunteer or that I will decide to do it myself. :-)
tahoe-lafs modified the milestone from undecided to 1.8.0 2010-05-26 14:51:17 +00:00
tahoe-lafs modified the milestone from 1.8.0 to soon 2010-08-10 03:53:20 +00:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: tahoe-lafs/trac-2024-07-25#394
No description provided.