The next phase of the measurement study has me generating a runtime graph
of the network, whose edges are weighted acording to some measured
property -- ie, latency, loss, hops, etc.
Previously I'd thought to separately use both latency and loss (ie, do
multiple alternate path measurements for the same path). This is proving
to be too expensive, pushing me towards using one single metric.
Tom had recommended using the Savage/Cardwell power metric. Anyone else
have suggestions on a good metric?
-John
---------- Forwarded message ----------
Date: Mon, 5 Oct 1998 15:51:18 -0700 (PDT)
From: Tom Anderson <tom@emigrant>
To: geigudr@cs.washington.edu
Subject: Re: one other thing...
i got hammered at MIT for the fact that the latency graph
is optimized for latency, and the drop rate graph is optimized
for drops, but there is no guarantee you can get both.
I'd rather get group feedback on this one. Can you pose it as
a design question to the group?
tom