Hi all,
To further back this up, since upgrading one of our doors to jdk1.5.0_10
at the end of February I have seen improved memory usage. Previously the
node would start swapping out after only a few days of consistent use.
This no longer appears to be the case.
Cheers,
Greig
Derek Ross wrote:
> After an enjoyable and productive afternoon playing gridftp door restart
> Whac-a-mole, I upgraded one of our gridftp doors to use jdk1.5.0_11
> rather than j2sdk1.4.2_12, and restarted it and another that had failed
> at the same time. 3 hours later the control had fallen over; the
> upgraded door is now at 7 hours uptime. It also appeared to be using
> markedly less threads.
>
> GFTP-gftp0444 gridftp-gftp0444Domain 0 29 88 msec
> 03/14 19:44:42 production-1-7-0(1.16)
> GFTP-gftp0445 gridftp-gftp0445Domain 0 613 139 msec
> 03/14 19:45:09 production-1-7-0(1.16)
> GFTP-gftp0446 gridftp-gftp0446Domain 0 600 136 msec
> 03/14 19:46:08 production-1-7-0(1.16)
>
> Above is after the next batch of restarts, copied from the dCache
> cellInfo page, gftp0444 is now using java 1.5, 445 and 446 aren't, the
> fourth column is claimed to be the number of threads in use.
>
> So if other sites are seeing problems with gridftp doors running out of
> memory they may want to think about upgrading the java version.
>
> Derek
|