[ https://issues.apache.org/jira/browse/HARMONY-5722?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Aleksey Shipilev updated HARMONY-5722:
--------------------------------------

    Description: 
For now, OIS and OOS use JNI stubs for accessing fields. It's bad for several reasons:
 a. infers a lot of JNI calls
 b. creates a lot of strings when looking up the field id.

This issue moves setField/getField functionality to more optimized API.

  was:
For now, OIS and OOS use JNI for accessing fields. It's bad for several reasons:
 a. infers a lot of JNI calls
 b. creates a lot of strings when looking up the field id.

This issue moves setField/getField functionality to Reflection API.

        Summary: [classlib][luni][performance] ObjectInputStream/ObjectOutputStream can use optimized API for accessing fields  (was: [classlib][luni][performance] ObjectInputStream/ObjectOutputStream can use Reflection API for setting/getting fields)

> [classlib][luni][performance] ObjectInputStream/ObjectOutputStream can use optimized API for accessing fields
> -------------------------------------------------------------------------------------------------------------
>
>                 Key: HARMONY-5722
>                 URL: https://issues.apache.org/jira/browse/HARMONY-5722
>             Project: Harmony
>          Issue Type: Improvement
>          Components: Classlib
>            Reporter: Aleksey Shipilev
>         Attachments: cl-ois-readfieldvalues-rc1.patch, cl-OIS_OOS-reflection-rc1.patch
>
>
> For now, OIS and OOS use JNI stubs for accessing fields. It's bad for several reasons:
>  a. infers a lot of JNI calls
>  b. creates a lot of strings when looking up the field id.
> This issue moves setField/getField functionality to more optimized API.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.