CMPUT 393 · Sprint 2 measurement service
a helpful tool, not a guaranteed servicePaste the public IPv6 address of one of your two systems and your course token. The service checks that system against the full 50M-event history on ranges you do not see.
Measure resets your instance. Right after the load run the service logs in with the course autograder key and hard-resets the box, the way a power cut would. Durable events/s is what your dashboard still reports afterwards, over the run's duration. Your service must come back on boot on its own.
One run per address at a time. Ranges are drawn fresh per run; a failure tells you the report, the range, what was expected and what you returned. Everyone submits at once the night before a deadline — that is the worst time to first find out whether your system answers at all.
Your past runs: /me?token=YOUR-TOKEN