Skip to content

Per-channel mutexes #422

Closed
Closed

Description

@TheBlueMatt

We should move channels into their own mutexes in ChannelManager, both for performance, and to make reasoning about things like #398 easier. I think the correct way is to have per-channel pending_msg_events queue and then have the cross-channel events (forward_htlcs and claimable_htlcs) live in their own mutexes. While we're at it, we should index channel ids by peer pubkeys, fixing #105.

Activity

  1. added this to the 0.2 milestone on Dec 14, 2019
  2. ariard commented on Jun 5, 2020

    @ariard
  3. TheBlueMatt commented on Oct 15, 2020

    @TheBlueMatt
    CollaboratorAuthor

    Note that if/when we do this we'll probably need to add per-ChannelMonitor locks in ChainMonitor as otherwise we'll just end up bottlenecked on Persister update time.

  4. TheBlueMatt commented on May 9, 2023

    @TheBlueMatt
    CollaboratorAuthor

    We did this!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions