Right now, for network workloads we basically have to use a trace (for IO we have a synthetic language, but it's crusty...). For simple benchmarks we could just roll our own.

The goal here is to provide a non-internal codes-workload plugin that users can provide function pointers to. You could imagine implementing a simple nearest-neighbor benchmark this way, among other things.

Really, the interface for providing codes-workload implementations should be user-visible and added to at runtime, but that might be more work... I'll probably take the path of least resistance for expedience.