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

rcmgr: use autoscaling limits #1637

Merged
merged 1 commit into from
Jul 3, 2022
Merged

rcmgr: use autoscaling limits #1637

merged 1 commit into from
Jul 3, 2022

Conversation

marten-seemann
Copy link
Contributor

Copy link
Collaborator

@MarcoPolo MarcoPolo left a comment

Choose a reason for hiding this comment

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

looks one question that’s not a blocker because it matches the old behavior

setProtocolLimits(limiter, holepunch.Protocol,
limiter.DefaultProtocolLimits.WithMemoryLimit(1, 4<<20, 64<<20),
peerLimit(2, 2, 2))
addServiceAndProtocolLimit(config,
Copy link
Collaborator

Choose a reason for hiding this comment

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

I know this was what the old code did, but why do we need to set both the service and protocol limit? Shouldn’t the service limit cover the protocol? And/or shouldn’t the protocol limit cover the service?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Yes, for services that use a single protocol. Identify uses multiple protocol IDs, so at least in theory, it could make sense to set separate limits.

@MarcoPolo
Copy link
Collaborator

Don’t forget to update the resource manager and this PR’s go.mod before merge

@marten-seemann marten-seemann merged commit e477efd into master Jul 3, 2022
@MarcoPolo MarcoPolo mentioned this pull request Jul 7, 2022
41 tasks
@ajnavarro ajnavarro mentioned this pull request Aug 24, 2022
72 tasks
@marten-seemann marten-seemann deleted the rcmgr-auto-scaling branch November 8, 2022 14:01
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.

2 participants