Skip to main content
R
RotechIT
Inspiring
August 29, 2014
Answered

How to stop AMS 5 from filling up the server memory? (multiple processes of ./amsmaster - console never seem to close...)

  • August 29, 2014
  • 1 reply
  • 542 views

When the server is booted, it starts off loading very little memory.
As people watch streams, memory use gradually increases. And increases!  Right now, only 22 MB free.

But with only 10 people currently watching streams, I still have 100+ processes open.

It seems these (caches?) open but never close - like there is no garbage collection.

I appreciate the value of caches, but how can I limit the memory used by AMS??

I would like to reserve a little for other processes... I'm getting nervous when it approaches the SWAP-zone...

(this is AMS 5 on Centos 6.3, BTW)

This topic has been closed for replies.
Correct answer hparmar

You said I still have 100+ processes open....I guess you mean threads(a.k.a LWPs on Linux)


Generally if a amscore does not have nay pending connections it dies off on its own...However number of threads i.e LWPs won't die down, since they are actually threads of an active process.

One way to shutdown amscore peridoically is to set appropriate RollOver and MaxCore values inside LifeTime Tag of Application.xml...However note that when ever a core rolls any active connections on it will be terminated...Thus Rollover period should be larger that largest possible connection/playback duration in order to prevent any surprise to any end user.

1 reply

H
Adobe Employee
hparmarCorrect answer
Adobe Employee
September 4, 2014

You said I still have 100+ processes open....I guess you mean threads(a.k.a LWPs on Linux)


Generally if a amscore does not have nay pending connections it dies off on its own...However number of threads i.e LWPs won't die down, since they are actually threads of an active process.

One way to shutdown amscore peridoically is to set appropriate RollOver and MaxCore values inside LifeTime Tag of Application.xml...However note that when ever a core rolls any active connections on it will be terminated...Thus Rollover period should be larger that largest possible connection/playback duration in order to prevent any surprise to any end user.

    R
    RotechITAuthor
    Inspiring
    September 4, 2014

    Yes, I meant threads! :-) Thanks for the hints

    Terms & ConditionsAccessibility statement
    Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices