0001782: Watchdog uses too much memory

Viewing Issue Advanced Details [ Jump to Notes ]

[ View Simple ] [ Issue History ] [ Print ]

Category

Severity

Reproducibility

Date Submitted

Last Update

0001782

[Resin]

minor

always

06-06-07 11:32

06-06-07 17:02

Reporter

sam

View Status

public

Assigned To

ferg

Priority

urgent

Resolution

fixed

Platform

Status

closed

Projection

none

OS Version

ETA

none

Fixed in Version

3.1.2

Product Version

3.1.1

Product Build

Summary

0001782: Watchdog uses too much memory

Description

(rep by M Schmidt)

I know in 3.1 you switched to a Java watchdog process.
Unfortuantely, this process seems a bit heavy. Its using 200M resident
memory and 1500M virtual. Is there a way to slim that puppy down a
bit? The nice thing about the perl script was that it didn't use much
memory.

Steps To Reproduce

Additional Information

Attached Files

Relationships

Notes
(0002018) sam 06-06-07 11:38	(rep by R Ross) Maybe we haven't been aggressive enough in trying to reduce the watchdog's footprint. Here are the watchdog-arg values we're using. Can we trim this back even further? <watchdog-arg>-Dcom.sun.management.jmxremote.port=9003</watchdog-arg> <watchdog-arg>-Dcom.sun.management.jmxremote</watchdog-arg> <watchdog-arg>-Xmx64m</watchdog-arg> <watchdog-arg>-Xss256k</watchdog-arg> <watchdog-arg>-XX:MaxPermSize=25m</watchdog-arg> It does seem to be keeping a lot of threads alive (possibly in order to support the JMX remote).

(0002020) ferg 06-06-07 17:02	Reduced defaults and number of threads, but really this is a Java runtime issue, not primarily a Resin issue.

Issue History
Date Modified	Username	Field	Change
06-06-07 11:33	sam	New Issue
06-06-07 11:38	sam	Note Added: 0002018
06-06-07 17:02	ferg	Note Added: 0002020
06-06-07 17:02	ferg	Assigned To	=> ferg
06-06-07 17:02	ferg	Status	new => closed
06-06-07 17:02	ferg	Resolution	open => fixed
06-06-07 17:02	ferg	Fixed in Version	=> 3.1.2

Mantis 1.0.0rc3[^]

31 total queries executed.
27 unique queries executed.