per-invocation setup for mutable data

[Travis Downs]

Thanks! I went with (2) since it's a bit more transparent (i.e., I don't
have to worry if I'm saturating the timestamp mechanism or whatever). As it
turns out, System.arraycopy is just really fast and made up a negligible
portion of the benchmark anyway.

On Wed, Dec 14, 2016 at 5:29 AM, Aleksey Shipilev <shade at redhat.com> wrote:

> On 12/14/2016 12:27 PM, Aleksey Shipilev wrote:
> > These are the only good options. Pick
>
> ...your poison :)
>
> -Aleksey
>
> P.S. Stupid keyboard shortcuts.
>
>