RFR: 8247532: Records deserialization is slow
Chris Hegarty
chris.hegarty at oracle.com
Mon Jun 15 12:47:38 UTC 2020
> On 15 Jun 2020, at 10:06, Peter Levart <peter.levart at gmail.com> wrote:
>
> Hi Chris,
>
> Maybe I stamped "Enchancement" just because it does not represent a logical bug, but 16x regression compared to the same feature with classes could be characterized as performance "bug", right?
That would be the categorisation that I would use.
-Chris.
>
> Peter
>
> On 6/15/20 10:37 AM, Chris Hegarty wrote:
>> Hi Peter,
>>
>> Thank you for doing this, it is really appreciated. I’m going to take this patch and run it in my local environment, after which I’ll post a reply here.
>>
>> > So WDYT? Since this is still a preview feature in JDK15, is it possible to squeeze it into JDK15?
>>
>> I think that such a change is a reasonable candidate for consideration in RDP 1. I see that the issue in JIRA is currently an Enhancement. Is it really an enhancement? If so, then it can follow the LERP [1]. Otherwise, if a regular bug between P1-P3 (inclusive), it can be integrated when reviewed and ready.
>>
>> -Chris.
>>
>> [1] https://openjdk.java.net/jeps/3#Late-Enhancement-Request-Process <https://openjdk.java.net/jeps/3#Late-Enhancement-Request-Process>
>>
>>> On 14 Jun 2020, at 22:34, Peter Levart <peter.levart at gmail.com <mailto:peter.levart at gmail.com>> wrote:
>>>
>>> So, here's new webrev incorporating Johannes' suggestion:
>>>
>>>
>>> http://cr.openjdk.java.net/~plevart/jdk-dev/RecordsDeserialization/webrev.02/ <http://cr.openjdk.java.net/~plevart/jdk-dev/RecordsDeserialization/webrev.02/>
>>>
>>
>
More information about the core-libs-dev
mailing list