On Thu, 10 Dec 2020 14:01:56 GMT, Jorn Vernee wrote:
>> While the updated set of scenarios covered by this benchmark is
>> reasonably (and vastly improves coverage), I find myself reluctant to
>> add the last remaining buffer property - read-only views. It's time to
>> template the generation of
On Thu, 10 Dec 2020 09:46:07 GMT, Chris Hegarty wrote:
>> Marked as reviewed by bpb (Reviewer).
>
> While the updated set of scenarios covered by this benchmark is
> reasonably (and vastly improves coverage), I find myself reluctant to
> add the last remaining buffer property - read-only views.
On Mon, 30 Nov 2020 20:54:09 GMT, Brian Burkhalter wrote:
>> Chris Hegarty has updated the pull request incrementally with two additional
>> commits since the last revision:
>>
>> - Add explicitly allocated heap carrier buffer tests
>> - Replace Single with Loop
>
> Marked as reviewed by bpb
On Mon, 30 Nov 2020 13:39:12 GMT, Chris Hegarty wrote:
>> The ByteBuffers micro benchmark seems to be a little dated.
>>
>> It should be a useful resource to leverage when analysing the performance
>> impact of any potential implementation changes in the byte buffer classes.
>> More
> The ByteBuffers micro benchmark seems to be a little dated.
>
> It should be a useful resource to leverage when analysing the performance
> impact of any potential implementation changes in the byte buffer classes.
> More specifically, the impact of such changes on the performance of sharp