Skip to content

Investigate max connection settings #3155

@moritzkiefer-da

Description

@moritzkiefer-da

See https://docs.digitalasset.com/operate/3.3/howtos/optimize/storage.html#max-connection-settings

For the participant we set it to 32 but we run with 4 CPUs mostly which is definitely much higher than expected.

From Ratko

Effectively max(num_connections) = 2*num_db_threads + a bit.
And the default allocation of connections is not great. In the past we often ended up at (N,N,N) (see https://github.com/DACH-NY/canton/blob/main/community/app/src/pack/config/participant.conf#L41-L46)
The reason is that giving too many db connections to the node means that you get contention on the database side, so your queries have to wait there.

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