Bug #3886
Metacat perfomance analysis
Start date:
03/12/2009
Due date:
% Done:
0%
Estimated time:
Bugzilla-Id:
3886
Description
Metacat is using a lot of memory on production and seems to use many db connections. We should monitor and determine why.
This ticket should be split into separate tickets if that makes sense.
History
#1 Updated by Michael Daigle over 11 years ago
Made a fix to the way the FileUtil reads in files. Otherwise, the monitors made it look like tomcat was using more memory than it was, because the jvm will keep memory once it's allocated, even though gc is cleaning it up.
#2 Updated by Redmine Admin over 7 years ago
Original Bugzilla ID was 3886