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

Posted to issues@ignite.apache.org by "Aleksandr (Jira)" <ji...@apache.org> on 2025/01/07 16:10:00 UTC

[jira] [Resolved] (IGNITE-24166) EventLog. Fix ChannelRegistry implementation performance issues.

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

Aleksandr resolved IGNITE-24166.
--------------------------------
    Resolution: Duplicate

IGNITE-24163

> EventLog. Fix ChannelRegistry implementation performance issues.
> ----------------------------------------------------------------
>
>                 Key: IGNITE-24166
>                 URL: https://issues.apache.org/jira/browse/IGNITE-24166
>             Project: Ignite
>          Issue Type: Bug
>            Reporter: Andrey Mashenkov
>            Priority: Blocker
>              Labels: ignite-3, performance
>
> Every `EventLogImpl.log()` method call causes `ConfigurationBasedChannelRegistry.findAllChannelsByEventType()` call on the hot path.
> The last one may return a copy of cached collection, which is designed to be immutable, by no reason.
> The cache is updated from another thread when cluster configuration changed, which is rarely happened. 
> A new caches can be constructed outside the lock, and just replaced with new instances under the lock.
> Let's implement copy-on-write properly.



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