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

Posted to issues@ignite.apache.org by "Ivan Bessonov (Jira)" <ji...@apache.org> on 2023/04/28 08:15:00 UTC

[jira] [Resolved] (IGNITE-18867) Optimize getting head in org.apache.ignite.internal.storage.pagememory.mv.gc.GcQueue

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

Ivan Bessonov resolved IGNITE-18867.
------------------------------------
    Resolution: Won't Fix

Read and remove are separated by explicit lock now. We can't implement current issue

> Optimize getting head in org.apache.ignite.internal.storage.pagememory.mv.gc.GcQueue
> ------------------------------------------------------------------------------------
>
>                 Key: IGNITE-18867
>                 URL: https://issues.apache.org/jira/browse/IGNITE-18867
>             Project: Ignite
>          Issue Type: Improvement
>            Reporter: Kirill Tkalenko
>            Priority: Minor
>              Labels: ignite-3, tech-debt
>
> I think that we could improve *org.apache.ignite.internal.storage.pagememory.mv.gc.GcQueue#getFirst* so that it not only gives the first element, but also immediately removes it from the tree.



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