[KULRICE-5942] See if we can improve our cache flushing with new Spring cache annotations Created: 09/Nov/11 Updated: 23/Feb/12 Resolved: 10/Jan/12
|Project:||Kuali Rice Development|
|Fix Version/s:||2.0.0-rc1, 2.0|
|Security Level:||Public (Public: Anyone can view)|
|Reporter:||Jeremy Hanson||Assignee:||Jeremy Hanson|
|Remaining Estimate:||Not Specified|
|Time Spent:||Not Specified|
|Original Estimate:||Not Specified|
|KAI Review Status:||Not Required|
|KTI Review Status:||Not Required|
Spring 3.1RC2 allows us to use a finer grained cache flushing. Seems like it could be useful for performance tuning.
We should investigate using this and make appropriate changes
|Comment by Jeremy Hanson [ 10/Jan/12 ]|
The answer is that we can improve on things a bit with this, in most cases our caches/cache keys are too complex to do a lot of this stuff, and with the nesting of objects (doc types, routing rules, membership stuff), our only real answer is to do full cache flushes in many instances.
That said, some work was done to clean things up a bit.
|Comment by Jessica Coltrin (Inactive) [ 23/Feb/12 ]|
Closing since these items are now in the release notes.