| Summary: | RFT performance improvements | ||
|---|---|---|---|
| Product: | RFT | Reporter: | Martin Feller <feller@mcs.anl.gov> |
| Component: | Campaign | Assignee: | Ravi Madduri <madduri@mcs.anl.gov> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | ajay_net1@hotmail.com, allcock@mcs.anl.gov, feller@mcs.anl.gov, gawor@mcs.anl.gov, lane@mcs.anl.gov, smartin@mcs.anl.gov |
| Priority: | P3 | ||
| Version: | development | ||
| Target Milestone: | 4.0.4 | ||
| Hardware: | PC | ||
| OS: | Linux | ||
| Bug Depends on: | |||
| Bug Blocks: | 4664 | ||
| Attachments: |
new logging class
patch |
||
Created an attachment (id=1044) [details]
new logging class
Created an attachment (id=1045) [details]
patch
In the last two comments I attached are two files: a new java code file
'MyPerformanceLog.java' (new logging class) and a patch for GT 4.0.3
to fix the problem.
First copy 'MyPerformanceLog.java' to
ws-transfer/reliable/service/java/source/src/org/globus/transfer/reliable/service/
Then the patch 'javaCode.patch' must be applied to the code in the directory
ws-transfer/reliable/service/java/source/ with
patch < javaCode.patch
If not already done all records of the table 'restart' in the rft database
should be removed. SQL command for this after a successful login to the
database system and selection of the database 'rft_database':
delete from restart;
I understand this has been committed to the 4 0 branch, so will be in 4.0.4. But still needs to be committed to the trunk. -Stu
Martin, Ravi, what more needs to be done here?
I don't remember this at all, was it really me who wrote this? (-: I guess this was the problem with the 800000 records in the RFT database, right? I didn't commit anything to RFT regarding this topic. But there are still some database issues. I can't precisely say what goes wrong, but the database still heaps up, not as dramatically as last time, but a little bit. I assume that records don't get cleaned up when transfers are interrupted. So maybe something with the lifetime of transfer resource goes wrong???
This fix has been released in 4.0.4, 4.0.5 and 4.0.6. Marking Fixed.