Actions
Bug #4475
closed
Promise generation process should not lose time by forking to run "/bin/true"
Status:
Released
Priority:
3
Assignee:
Category:
Performance and scalability
Target version:
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:
Description
See http://www.rudder-project.org/redmine/issues/4427#note-4
Idea: before trying to do cf-promise on generated promises, check for "/bin/true" and just continue on that case, without actually forking to get an "ok".
Updated by François ARMAND almost 11 years ago
- Category changed from Web - Config management to Performance and scalability
- Status changed from 8 to In progress
Updated by François ARMAND almost 11 years ago
- Pull Request set to https://github.com/Normation/rudder/pull/443
PR here: https://github.com/Normation/rudder/pull/443
Quite simple !
Updated by François ARMAND almost 11 years ago
- Status changed from In progress to Pending technical review
- Assignee changed from François ARMAND to Nicolas CHARLES
Updated by François ARMAND almost 11 years ago
- Status changed from Pending technical review to Pending release
- % Done changed from 0 to 100
Applied in changeset 5ffa00f57fe4f8e60e1e80b82caa3f54b6000190.
Updated by Nicolas CHARLES almost 11 years ago
Applied in changeset 1dcf4ce5dfbfeec70d562b8e901bcc1b14cb7c32.
Updated by Vincent MEMBRÉ almost 11 years ago
- Tracker changed from Bug to User story
- Subject changed from In promise generation, don't fork for "/bin/true" to Speed up promise generation, don't fork when using "/bin/true" instead of "cf-promises"
Updated by Vincent MEMBRÉ almost 11 years ago
- Tracker changed from User story to Bug
- Pull Request set to https://github.com/Normation/rudder/pull/443
Updated by Vincent MEMBRÉ almost 11 years ago
- Subject changed from Speed up promise generation, don't fork when using "/bin/true" instead of "cf-promises" to Promise generation process should not lose time by forking to run "/bin/true"
Updated by Vincent MEMBRÉ over 10 years ago
- Status changed from Pending release to Released
This bug has been fixed in Rudder 2.10.0~beta1, which was released today.
Check out:
The release announcement: http://www.rudder-project.org/pipermail/rudder-announce/2014-March/000084.html
The full ChangeLog: http://www.rudder-project.org/foswiki/bin/view/System/Documentation:ChangeLog210
Download information: https://www.rudder-project.org/site/get-rudder/downloads/
Updated by Benoît PECCATTE about 9 years ago
- Target version changed from 2.10.0~beta1 to 2.6.12
Actions