Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Increase secure session pool size to 4096 #88

Merged
merged 2 commits into from
Jul 1, 2024

Conversation

agners
Copy link
Collaborator

@agners agners commented Jul 1, 2024

Increase the maximum amount of secure sessions to 4 times the device limit. This allows to have multiple sessions per device (if required) or multiple fabrics of up to 1024 devices.

The size of a secure session is currently 264 bytes, so this will increase memory usage by about 1MB.

While at it, also increase the number of outgoing CASE sessions can be simutaneously negotiated from the default 16 to 32 (CHIP_CONFIG_CONTROLLER_MAX_ACTIVE_CASE_CLIENTS).

Increase the maximum amount of secure sessions to 4 times the device
limit. This allows to have multiple sessions per device (if required) or
multiple fabrics of up to 1024 devices.

The size of a secure session is currently 264 bytes, so this will
increase memory usage by about 1MB.
CHIPProjectConfig.h Outdated Show resolved Hide resolved
@@ -59,6 +59,8 @@
// Home Assistant Python Matter server specific configs
#define CHIP_EXCHANGE_NODE_ID_LOGGING 1
#define CHIP_CONFIG_CONTROLLER_MAX_ACTIVE_DEVICES 1024
#define CHIP_CONFIG_CONTROLLER_MAX_ACTIVE_CASE_CLIENTS 32
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

what does this do ? as this feels a bit on the low side as well to me ?!
You almost think this should at least be max devices x 2

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is "number of outgoing CASE sessions can be simutaneously negotiated". We currently setup 5 at a time at max, so this is quite a bit higher. But yeah maybe we can bump it a bit more too.

Co-authored-by: Marcel van der Veldt <m.vanderveldt@outlook.com>
@agners agners merged commit 7b2bfcc into release Jul 1, 2024
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants