$Id: TODO,v 1.4 1994/11/26 00:36:39 lm Exp $

The lat_fs and lat_pagefault numbers are not being reported yet.

Documentation on porting.

Check that file size is right in the benchmarking system.

Compiler version info included in results.

Assembler output for the files that need it.

memory store latency (complex)
	Why can't I just use the read one and make it write?
	Well, because the read one is list oriented and I need to figure
	out reasonable math for the write case.  The read one is a load
	per statement whereas the write one will be more work, I think.

RPC numbers reserved for the benchmark.

Check all the error outputs and make sure they are consistent.

Each of these tests could take a quick stab at guessing the answer
and adjust N to match.  For example, the networking latency numbers
can vary from 400 to 15,000 usecs, depending on the network.

On all the normalized graphs, make sure that they mean the same thing.
I do not think that the bandwidth measurements are "correct" in this
sense.
