Actions
Architecture #4521
closed
When generating promises, use a cache for template file
Status:
Released
Priority:
1 (highest)
Assignee:
Category:
Performance and scalability
Target version:
Pull Request:
Effort required:
Name check:
Fix check:
Regression:
Description
For now, we don't cache template file when generating promises, so we read the template each time it is needed to write a promise for a node.
We could cache them in a Map[template id -> template content], trading I/O for memory (and as Linux is quite good in caching, perhaps actually, we don't trade so much I/O to memory).
Updated by François ARMAND over 10 years ago
- Category set to Performance and scalability
- Status changed from New to 8
- Priority changed from N/A to 2
- Target version set to 2.10.0~beta1
Updated by François ARMAND over 10 years ago
- Status changed from 8 to 13
- Assignee set to François ARMAND
Updated by François ARMAND over 10 years ago
- Tracker changed from User story to Architecture
Updated by Jonathan CLARKE over 10 years ago
- Status changed from 12 to Pending release
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/
Actions