Tasks #549
Check scopes -> spread groupnames cache
| Status: | Resolved | Start date: | 09/05/2011 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: | J. Wienke | % Done: | 0% | |
| Category: | C++ | Estimated time: | 1.00 hour | |
| Target version: | 0.5 |
Description
Check scopes -> spread groupnames cache
- Check for concurrent access
- Limit size
Associated revisions
Cache for scopes -> spread groupnames
refs #549
Flush cache if flooded
refs #549
History
#1 Updated by J. Wienke over 12 years ago
Is this a result of the performance optimization? Or what is the reason to do this?
#2 Updated by J. Moringen over 12 years ago
The introduction of the cache is an optimization. Currently, there is no concrete reason to suspect that the cache causes incorrect behavior. However, we have to make sure there are no threading issues and the cache does not grow indefinitely.
#3 Updated by J. Wienke over 12 years ago
Hm, could this be the performance optimizatio ncategory as well? Because other tickets are in that category.
#4 Updated by J. Moringen over 12 years ago
Ideally, it would be in C++ and Performance Optimization.
#5 Updated by J. Wienke over 12 years ago
- Status changed from New to In Progress
#6 Updated by J. Wienke over 12 years ago
- Assignee set to J. Wienke
#7 Updated by J. Wienke over 12 years ago
- Status changed from In Progress to Resolved
Fixed in r2717.
However, this probably decreases the performance again. Have a look at the commit message.
#8 Updated by J. Moringen over 12 years ago
- Target version changed from rsb-0.10 to 0.5