Dear GN Users,
I'm having trouble keeping GN running after several hours of use (I have
adjusted my 'default user session' length). When I look in my task
manager every click/action increases the used memory (normal) but then
backing up to the home page or reducing my search to the standard search
from the the advanced, the memory used does not decrease. I think the
problem is that the java.exe is not releasing unused memory, does this
code run a 'garbage collector'? I also have GN installed on a remote
server to support multiple users, to make this setup run effectively the
'start server' file runs constantly in the background on the remote
server, so that my users do not have to access the remote server with
every login to GN. Is this memory problem the result of the 'start
server' file being open for extended periods of time? How have other
users gotten around this problem when working with multiple users?
Thanks,
Laura
_______________________________
Laura Cagney
Grand Canyon Monitoring and Research Center
Dear GN Users,
Dear Laura,
I'm having trouble keeping GN running after several hours of use
(I have
adjusted my 'default user session' length). When I look in my task
manager every click/action increases the used memory (normal) but then
backing up to the home page or reducing my search to the standard
search
from the the advanced, the memory used does not decrease. I think the
my feeling is that you have a non-problem here. In any case, this does
not seem GN specific to me.
What you are seeing are general problems of software giving memory back
to the operating system. This is something that does not work very well
AFAIK. However, the java runtime internal memory management is not
affected by this. The garbage collection is still working and should
free memory for internal re-usage. Its just that you cannot see it from
outside.
Threads are another issue. On linux you see them sometimes as processes
of their own, each seemingly occupying memory, although they actually
share it, but this is not your "problem".
The way to address this are probably playing with the parameters of
the java virtual machine or searching for general java memory management
hints.
best regards
Timo
--
Timo Pröscholdt
Program Officer, WMO Information System (WIS)
Observing and Information Systems Department
World Meteorological Organization
Tel: +41 22 730 81 76
Cell: +41 77 40 63 554
e-mail: tproescholdt@anonymised.com