You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@daffodil.apache.org by "Steve Lawrence (Jira)" <ji...@apache.org> on 2021/08/23 13:32:00 UTC

[jira] [Resolved] (DAFFODIL-1432) Performance: TLRegistersPool is a thread local, but we can keep this pool in the pstate

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

Steve Lawrence resolved DAFFODIL-1432.
--------------------------------------
    Resolution: Duplicate

This was fixed as part of DAFFODIL-2034 in commit 3868989577be2e9b85194cc866de9e29cf4c574e. Marking as duplicate.

> Performance: TLRegistersPool is a thread local, but we can keep this pool in the pstate
> ---------------------------------------------------------------------------------------
>
>                 Key: DAFFODIL-1432
>                 URL: https://issues.apache.org/jira/browse/DAFFODIL-1432
>             Project: Daffodil
>          Issue Type: Improvement
>          Components: Back End, Clean Ups, Performance
>            Reporter: Mike Beckerle
>            Priority: Minor
>
> TLRegistersPool is a thread local, but we can keep this pool in the pstate to avoid the overhead of the hash-table lookup for ThreadLocal.get. This is true anywhere we have the PState available (or UState for unparser), and we are using any Thread-local thing.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)