[
https://issues.apache.org/jira/browse/IGNITE-19487?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexey Scherbakov updated IGNITE-19487:
---------------------------------------
Description:
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
* storing lock key hashes.
* limiting the number of lock table slots (lock key is hashed to slot)
[1] https://trustworthy.systems/publications/nicta_full_text/6465.pdf
was:
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
* storing lock key hashes.
* limiting the number of lock table slots
[1] https://trustworthy.systems/publications/nicta_full_text/6465.pdf
> 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
> * storing lock key hashes.
> * limiting the number of lock table slots (lock key is hashed to slot)
> [1] https://trustworthy.systems/publications/nicta_full_text/6465.pdf
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
