RFR: 8247532: Records deserialization is slow

[Chris Hegarty]

> On 17 Jun 2020, at 06:44, Peter Levart <peter.levart at gmail.com> wrote:
>>> ..
>> If there is a way for a test to compile several versions of the same (record) class and then produce byte streams with it, then we could simulate various class-evolution cases (field missing, surplus field, change of field type, etc...) without crafting the bytestream by hand. WDYT?
> 
> I have a better idea. The test could contain several different classes with different names that would be used to generated variations of serialized stream. Such streams could then be "patched" so they would contain the common target class name and then used to (attempt to) deserialize the target class. I'll try to devise such test…
> 
I think that could work. I’ll mock something up too, just for comparison purposes.

-Chris.