All new accounts created on Gitlab now require administrator approval. If you invite any collaborators, please let Flux staff know so they can approve the accounts.

Commit 5b9dbdfe authored by Robert Ricci's avatar Robert Ricci

Update scoring sheet

parent e62867bf
HW #3 Score:
XX / 4 : Question 1
One point for part (a); examples include messages sent, convergence
time, stretch, percentage of packets that end up in routing loops
One point for part (b); examples include throughput, latency, loss rate,
overhead due to headers or signaling, energy use, fairness
One point for part (c); examples include througput, IOPS, size, latency,
fairness, durability
One point for part (d); examples include throughput, false positive rate,
false negative rate
One point for part (a); examples include read and write throughput,
read and write latency, overhead spent on index structures, etc.
One point for part (b); examples include query throughput (for reads,
inserts, and updates), query latency, and resource consumption
(eg. CPU and RAM)
One point for part (c); examples include bandwidth consumed, latency (how
long do updates take to reach other clients), and accuracy (how
inconsistent is state between clients)
One point for part (d); examples include true and false positive rate,
true and false negative rate, throughput
One half point may be deducted per part for failing to explain the types of
questions the metric would help answer
XX / 6 : Question 2
Two points for discussion of data to request; good examples include
traces of connection/disconnection events, traces of calls, traces
of data sessions, traces of geographical locations, or aggregate
statistics covering any of the properties listed below
Two points for discussion of data to request; examples include traces
of packets or session, number of users over time, etc., and/or
aggregate statistics covering the above
Three points for discussion of properties to study; good examples include
peak number of users, variations at different timescales (seconds,
minutes, hours, days, weeks), distribution of users across access
points, data behavior including number of connections, rate of
connections, amount of data transfered per connection
average and peak number of users, variations at different timescales
(seconds, minutes, hours, days, weeks), resources consumed per user,
etc.
One point for stating assumptions about the change, or being
sufficiently general that no assumptions seem to be needed
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment