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

Fixes #15775: Performance problems with ZIO #2529

Conversation

fanf
Copy link
Member

@fanf fanf commented Oct 14, 2019

@fanf
Copy link
Member Author

fanf commented Oct 14, 2019

PR rebased

@fanf fanf force-pushed the bug_15775/performance_problems_with_zio branch from 84e1369 to 2def956 Compare October 14, 2019 22:30
@fanf
Copy link
Member Author

fanf commented Oct 14, 2019

PR updated with a new commit

@fanf fanf force-pushed the bug_15775/performance_problems_with_zio branch from d20f859 to fdbc8e6 Compare October 15, 2019 00:15
@fanf
Copy link
Member Author

fanf commented Oct 15, 2019

PR rebased

_ <- counters.sumTimeExpandeVar.update(_ + t2_1 - t2_0)
// And now, for each variable, eval - if needed - the result
expandedVars <- expandedVariables.accumulate { case (k, v) =>
//js lib is specific to the node os, bind here to not leak eval between vars
Copy link
Member

Choose a reason for hiding this comment

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

i think this could be done outside the flteredDraft.accumulate, as we are dealing node per node
but i don't think it would change much perf, but surely allocate less objects

@Normation-Quality-Assistant
Copy link
Contributor

OK, merging this PR

@Normation-Quality-Assistant Normation-Quality-Assistant merged commit fdbc8e6 into Normation:branches/rudder/6.0 Oct 15, 2019
@fanf fanf deleted the bug_15775/performance_problems_with_zio branch March 15, 2024 10:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
3 participants