Actions
Bug #4584
closed
Building node configuration in the promise generation process takes a lot of time
Status:
Rejected
Priority:
N/A
Assignee:
-
Category:
Performance and scalability
Target version:
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:
Description
Now that some major performance update were done (for ex. in #4242) in the promise generation process, the new bottleneck seems to be the node configuration generation.
It seems that in that process, the DeploymentService_buildNodeConfigurations#replaceNodeVars is taking ~90% of total time of that subtask.
So, it seems that we are doing something very wrong in the way we process ${rudder.XXX} parameters.
Updated by Vincent MEMBRÉ over 10 years ago
- Target version changed from 2.10.0~beta1 to 2.10.0
Updated by Vincent MEMBRÉ over 10 years ago
- Target version changed from 2.10.0 to 2.11.0~beta1
Updated by François ARMAND over 10 years ago
- Description updated (diff)
- Status changed from New to Rejected
Duplicated by #4778
Updated by Vincent MEMBRÉ over 10 years ago
- Status changed from Rejected to Released
This bug has been fixed in Rudder 2.11.0~beta1 that was released yesterday.
- announcement
- changelog
- Download information: https://www.rudder-project.org/site/get-rudder/downloads/
Updated by Vincent MEMBRÉ over 10 years ago
- Status changed from Released to Rejected
Actions