Bugzilla – Bug 2703
Implement record caching in RFT resource implementation
Last modified: 2005-03-01 21:38:24
You need to
before you can comment on or make changes to this bug.
In the present implementation, the next transfer that needs to be done is
retrieved from the database.
This will reduce the robustness of the transfers if the request size is close
to hundreds of thousands. A
simple caching mechanism that would reduce the number of queries run against
the database would
increase the performance quite a bit. This should be in place before 4.0
More care need to be taken to analyze memory foot print increase that may
result from this.
The cache size should be made configurable for 4.2