Skip to content

Added docs about cf-reactor performance - #3824

Merged
larsewi merged 2 commits into
cfengine:masterfrom
victormlg:reactor-limits
Nov 9, 2026
Merged

larsewi merged 2 commits into
cfengine:masterfrom
victormlg:reactor-limits

Conversation

@victormlg

Copy link
Copy Markdown
Contributor

No description provided.

Signed-off-by: Victor Moene <victor.moene@northern.tech>
**Notes:**

- Users and packages could not be added or removed fast enough to reach the limit of `cf-reactor`: these figures are lower bounds.
- Above the limit, `cf-reactor` doesn't lose events: they pile up in the queue and are handled late.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Does the queue ever get full? Will you eventually run out of memory?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

No, the queue cannot get full. Yes it will ran out of memory if too many events are coming.


**Notes:**

- Users and packages could not be added or removed fast enough to reach the limit of `cf-reactor`: these figures are lower bounds.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

You could use a fake package module that is faster.

@larsewi

larsewi commented Nov 5, 2026

Copy link
Copy Markdown
Contributor

Maybe a better way to measure this is: how fast can you setup and execute an empty bundle, and how fast is the "check" for each type. Everything else seems out of our control. E.g., what the then bundle is doing, or how slow the package manager is. Those things are not really cf-reactor limits.

@olehermanse

Copy link
Copy Markdown
Member

E.g., what the then bundle is doing, or how slow the package manager is. Those things are not really cf-reactor limits.

That's true, but I think real-world performance is what matters to users.

Clarified what cf-reactor’s performance depends on: the speed of the event type and the speed of the then bundle
Showed what then bundle was used for the experiments.

Signed-off-by: Victor Moene <victor.moene@northern.tech>

@larsewi larsewi left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

E.g., what the then bundle is doing, or how slow the package manager is. Those things are not really cf-reactor limits.

That's true, but I think real-world performance is what matters to users.

Still feels strange to base the limit of cf-reactor on how fast you can install or uninstall packages. But I guess the notes mention it. So it's fine by me.

@larsewi
larsewi merged commit e68ae86 into cfengine:master Nov 9, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

3 participants