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

Posted to issues@ignite.apache.org by "Alexey Scherbakov (Jira)" <ji...@apache.org> on 2023/05/16 17:00:00 UTC

[jira] [Updated] (IGNITE-19487) Optimize LockManager

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

Alexey Scherbakov updated IGNITE-19487:
---------------------------------------
    Labels: ignite-3  (was: )

> Optimize LockManager
> --------------------
>
>                 Key: IGNITE-19487
>                 URL: https://issues.apache.org/jira/browse/IGNITE-19487
>             Project: Ignite
>          Issue Type: Improvement
>            Reporter: Alexey Scherbakov
>            Priority: Major
>              Labels: ignite-3
>
> Currently LockManager is implemented on top of CHMT. This may not be optimal, some more advanced techniques should be investigated, like described in [1]. Additionally, lock manager memory consumption can be reduced by going offheap and storing lock key hashes.
> [1] https://trustworthy.systems/publications/nicta_full_text/6465.pdf 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)