...
- Latency under no-load
Input parameters - Object Size, Type of operation (Object vs Table, Read vs Write), Capacity of RAMCloud in use, Master failures, Object access distribution (Zipf?)
Output measured in - micro seconds
Measured end-to-end from the perspective of the client. - Latency under load
Input parameters - Number of operations under load, Object Size, Type of operation (Object vs Table, Read vs Write), Capacity of RAMCloud in use, Master failures, Object access distribution (Zipf?)
Output measured in - micro seconds
A pre-defined workload is first imposed on the system in terms of number of simultaneous operations. Latency measurements are then made for each type of operation. - Throughput of operations
Input parameters - Object Size distribution, Type of operation, Object access distribution, Capacity of RAMCloud in use, Master failures
Output measured in - number of object reads per second, number of object writes per second - Throughput of IO
Input parameters - Object Size distribution, Type of operation, Object access distribution, Capacity of RAMCloud in use, Master failures
Output measured in - number of client bytes reads per second, number of client byte writes per second (ideally should only include real content size and not count the overhead imposed by RAMCloud structures) - Simultaneous Connections
Input parameters - Number of masters, Number of client processes, Number of client machines
Output measured in - number of connectionsOf internal interest
- Number of rpcs
- Internal Hash-table size
- Actual DRAM used versus raw DRAM required for object contents
Simulated workload types
1- Banking Website
...