[PATCH] Add random memcpy test

[Carlos O'Donell]

On 06/03/2016 09:09 AM, Siddhesh Poyarekar wrote:
> PS: Whatever happened to the whole system benchmarking project?

It's growing slowly out of DJ's malloc benchmarking project? :-)

On dj/malloc we have the ability to:

- Trace malloc with minimal overhead during an application run.
- Save traces of stored data.
- Re-run trace in model simulator.
  - Allows you to play locally with malloc changes and see
    how they impact the saved workload.

The problem is that this scales very slowly API by API.

The whole system benchmarking project idea was that we would
take traces of the whole system and then feed that data back
as a workload that glibc can be tuned against.

We have scaled it back to 1 process from 1 system, and to
1 API from the whole library.

-- 
Cheers,
Carlos.