DX Application Performance Management

Expand all | Collapse all

How we can decrease memory utilization

  • 1.  How we can decrease memory utilization

    Posted 01-19-2018 05:05 AM

    Hi,

    How we can reduce memory utilization of collectors as well as MOM n webview.We have declared heap size of 4GB .But normally we received memory utilization alerts even for whose value is 8 GB.Any thing we can fix n resolve this issue permanently.

     

    P.S  You can also see below one.here we have given 15 GB.

    $ free -g
             total used free shared buffers cached
    Mem: 15    12       3       0          0       8

     

    2nd question

     

    >Always i am seeing "Cached data is of 4GB or more how can we clear it n how we can idetify what kind of data is under Cached.



  • 2.  Re: How we can decrease memory utilization

    Posted 01-19-2018 11:03 AM

    This is a duplicate of Duplicate Post: How we can decrease memory utilization   Please respond there



  • 3.  Re: How we can decrease memory utilization

    Posted 01-19-2018 11:35 AM

    Which one is the original? You've linked each backed to each other so I have no idea which to respond to.



  • 4.  Re: How we can decrease memory utilization

    Posted 01-19-2018 11:36 AM

    Please attach your LAX or post the contents here for review.

    What is the OS platform?



  • 5.  Re: How we can decrease memory utilization

    Posted 02-06-2018 02:53 AM

    Attahing Lax file.

    Webview :-

    # LaunchAnywhere (tm) Executable Properties File - Flexera Software LLC

    # LAX.APPLICATION.NAME
    # --------------------
    # the default name of this executable -- do not edit

    lax.application.name=Introscope_WebView


    # LAX.CLASS.PATH
    # --------------
    # the Java classpath necessary to run this application
    # Can be separated by colons (Mac OS/Unix) or semicolons (Windows)

    lax.class.path=launcher.jar:ext:lax.jar


    # LAX.COMMAND.LINE.ARGS
    # ---------------------
    # what will be passed to the main method -- be sure to quote arguments with spaces in them

    lax.command.line.args=$CMD_LINE_ARGUMENTS$ -consolelog -noExit -product com.wily.introscope.webview.server.product -install "./product/webview" -configuration "./product/webview/configuration"


    # LAX.DIR
    # -------
    # path to the directory holding LaunchAnywhere's native launcher

    lax.dir=./


    # LAX.MAIN.CLASS
    # --------------
    # the class that contains the main method for the application

    lax.main.class=org.eclipse.core.launcher.Main


    # LAX.MAIN.METHOD
    # ---------------
    # the method in the main class that will be invoked

    lax.main.method=main


    # LAX.NL.CURRENT.VM
    # -----------------
    # the VM to use for the next launch

    lax.nl.current.vm=jre/bin/java


    # LAX.NL.JAVA.LAUNCHER.MAIN.CLASS
    # -------------------------------
    # main class of LaunchAnywhere's java launcher -- do not adjust

    lax.nl.java.launcher.main.class=com.zerog.lax.LAX


    # LAX.NL.JAVA.LAUNCHER.MAIN.METHOD
    # --------------------------------
    # main method of LaunchAnywhere's java launcher -- do not adjust

    lax.nl.java.launcher.main.method=main


    # LAX.NL.JAVA.OPTION.ADDITIONAL
    # -----------------------------
    # place any optional Java arguments (such as heap size) here
    # Browser Agent Feature is not supported on the WebView Agent
    # If you are installing on AIX (with JRE7 or earlier), add the following switch
    # -XX:MaxPermSize=256m
    # Introscope Java Agent Arguments for WebView Monitor
    # -javaagent:./product/webview/agent/wily/Agent.jar -Dcom.wily.introscope.agentProfile=./product/webview/agent/wily/core/config/IntroscopeAgent.profile -Dcom.wily.introscope.wilyForWilyPrefix=com.wily -Djetty.home=./

    lax.nl.java.option.additional=-Xms4096m -Xmx4096m -Djava.awt.headless=true -Dorg.owasp.esapi.resources=./config/esapi -Dsun.java2d.noddraw=true -Dorg.osgi.framework.bootdelegation=org.apache.xpath


    # LAX.NL.MESSAGE.VM.NOT.LOADED
    # ----------------------------
    # message displayed in a user dialog if NO VM from the lax.nl.valid.vm.list can be found. Note: This property is internal to the InstallAnywhere launcher. Introscope has separate Java requirements. For more information, consult the "System Requirements" section of Introscope's user documentation.

    lax.nl.message.vm.not.loaded=LaunchAnywhere either could not find a Java VM, or the Java VM on this system is too old. LaunchAnywhere requires a Java 2 VM in order to launch Introscope.


    # LAX.NL.VALID.VM.LIST
    # --------------------
    # a string containing one or more of [ ALL JDK JRE J1 J2 JRE_J1 JDK_J1 JRE_J2 JDK_J2 MSJ ] delimited by spaces or commas. If the native launcher cannot find the current vm,
    # it will search for ones in this list

    lax.nl.valid.vm.list=J2


    # LAX.NL.WIN32.MICROSOFTVM.MIN.VERSION
    # ------------------------------------
    # The minimum version of Microsoft's VM this application will run against

    lax.nl.win32.microsoftvm.min.version=2750


    # LAX.ROOT.INSTALL.DIR
    # --------------------
    # path to the installdir magic folder

    lax.root.install.dir=.


    # LAX.STDERR.REDIRECT
    # -------------------
    # leave blank for no output, "console" to send to a console window,
    # and any path to a file to save to the file

    lax.stderr.redirect=console


    # LAX.STDIN.REDIRECT
    # ------------------
    # leave blank for no input, "console" to read from the console window,
    # and any path to a file to read from that file

    lax.stdin.redirect=console


    # LAX.STDOUT.REDIRECT
    # -------------------
    # leave blank for no output, "console" to send to a console window,
    # and any path to a file to save to the file

    lax.stdout.redirect=console


    # LAX.USER.DIR
    # ------------
    # left blank, this property will cause the native launcher to not
    # alter the platform default behavior for setting the user dir.
    # To override this you may set this property to a relative or absolute path.
    # Relative paths are relative to the launcher.

    lax.user.dir=./


    # LAX.VERSION
    # -----------
    # version of LaunchAnywhere that created this properties file

    lax.version=16.5

     

     

    MOM :-

     

    # LaunchAnywhere (tm) Executable Properties File - Flexera Software LLC

    # LAX.APPLICATION.NAME
    # --------------------
    # the default name of this executable -- do not edit

    lax.application.name=Introscope_Enterprise_Manager


    # LAX.CLASS.PATH
    # --------------
    # the Java classpath necessary to run this application
    # Can be separated by colons (Mac OS/Unix) or semicolons (Windows)

    lax.class.path=launcher.jar:ext:lax.jar


    # LAX.COMMAND.LINE.ARGS
    # ---------------------
    # what will be passed to the main method -- be sure to quote arguments with spaces in them

    lax.command.line.args=$CMD_LINE_ARGUMENTS$ -consolelog -noExit -product com.wily.introscope.em.product -install "./product/enterprisemanager" -configuration "./product/enterprisemanager/configuration"


    # LAX.DIR
    # -------
    # path to the directory holding LaunchAnywhere's native launcher

    lax.dir=./


    # LAX.MAIN.CLASS
    # --------------
    # the class that contains the main method for the application

    lax.main.class=org.eclipse.core.launcher.Main


    # LAX.MAIN.METHOD
    # ---------------
    # the method in the main class that will be invoked

    lax.main.method=main


    # LAX.NL.CURRENT.VM
    # -----------------
    # the VM to use for the next launch

    lax.nl.current.vm=jre/bin/java


    # LAX.NL.JAVA.LAUNCHER.MAIN.CLASS
    # -------------------------------
    # main class of LaunchAnywhere's java launcher -- do not adjust

    lax.nl.java.launcher.main.class=com.zerog.lax.LAX


    # LAX.NL.JAVA.LAUNCHER.MAIN.METHOD
    # --------------------------------
    # main method of LaunchAnywhere's java launcher -- do not adjust

    lax.nl.java.launcher.main.method=main


    # LAX.NL.JAVA.OPTION.ADDITIONAL
    # -----------------------------
    # place any optional Java arguments (such as heap size) here.
    # The following switches are recommended for 32-bit Sun JVMs:
    # -showversion -XX:CMSInitiatingOccupancyFraction=50 -Xss256k
    # The following switches are recommended for 64-bit Sun JVMs:
    # -Xss512k
    # If you are using both Hot Failover and the CEM UI,
    # add the following switch when starting the Secondary Introscope Enterprise Manager (or second Primary),
    # -Dosgi.clean=false
    # If you are installing on AIX (with JRE7 or earlier), add the following switch
    # -XX:MaxPermSize=256m
    # Set the lax java option additional values like: -Xms1024m -Xmx1024m -Djava.awt.headless=false -Dmail.mime.charset=UTF-8 -Dorg.owasp.esapi.resources=./config/esapi -XX:+UseConcMarkSweepGC -XX:+UseParNewGC

    #lax.nl.java.option.additional=-Xms1024m -Xmx1024m -Djava.awt.headless=true -Dmail.mime.charset=UTF-8 -Dorg.owasp.esapi.resources=./config/esapi -XX:+UseConcMarkSweepGC -XX:+UseParNewGC -Xss512k

    lax.nl.java.option.additional=-Xms8192m -Xmx8192m -Djava.awt.headless=true -Dmail.mime.charset=UTF-8 -Dorg.owasp.esapi.resources=./config/esapi -XX:+UseConcMarkSweepGC -XX:+UseParNewGC -Xss512k


    # LAX.NL.MESSAGE.VM.NOT.LOADED
    # ----------------------------
    # message displayed in a user dialog if NO VM from the lax.nl.valid.vm.list can be found. Note: This property is internal to the InstallAnywhere launcher. Introscope has separate Java requirements. For more information, consult the "System Requirements" section of Introscope's user documentation.

    lax.nl.message.vm.not.loaded=LaunchAnywhere either could not find a Java VM, or the Java VM on this system is too old. LaunchAnywhere requires a Java 2 VM in order to launch Introscope.


    # LAX.NL.VALID.VM.LIST
    # --------------------
    # a string containing one or more of [ ALL JDK JRE J1 J2 JRE_J1 JDK_J1 JRE_J2 JDK_J2 MSJ ] delimited by spaces or commas.
    # if the native launcher cannot find the current vm,
    # it will search for ones in this list

    lax.nl.valid.vm.list=J2


    # LAX.NL.WIN32.MICROSOFTVM.MIN.VERSION
    # ------------------------------------
    # The minimum version of Microsoft's VM this launcher will run with

    lax.nl.win32.microsoftvm.min.version=2750


    # LAX.ROOT.INSTALL.DIR
    # --------------------
    # path to the installdir magic folder

    lax.root.install.dir=.


    # LAX.STDERR.REDIRECT
    # -------------------
    # leave blank for no output, "console" to send to a console window,
    # and any path to a file to save to the file

    lax.stderr.redirect=console


    # LAX.STDIN.REDIRECT
    # ------------------
    # leave blank for no input, "console" to read from the console window,
    # and any path to a file to read from that file. Note: If you are running
    # the Enterprise Manager in nohup mode for Unix platforms, do NOT
    # change this setting, or the EM may fail to start. Should you choose
    # to change this setting to blank, you MUST disable Interactive Mode
    # in the IntroscopeEnterpriseManager.properties file.

    lax.stdin.redirect=console


    # LAX.STDOUT.REDIRECT
    # -------------------
    # leave blank for no output, "console" to send to a console window,
    # and any path to a file to save to the file

    lax.stdout.redirect=console


    # LAX.USER.DIR
    # ------------
    # left blank, this property will cause the native launcher to not
    # alter the platform default behavior for setting the user dir.
    # To override this you may set this property to a relative or absolute path.
    # Relative paths are relative to the launcher.

    lax.user.dir=./


    # LAX.VERSION
    # -----------
    # version of LaunchAnywhere that created this properties file

    lax.version=16.5



  • 6.  Re: How we can decrease memory utilization

    Posted 01-25-2018 11:50 AM

    What is setting off the alerts?  Cache is maintained by the kernel to speed up future operations.  It is released to the system when needed and shouldn't be considered used memory.  

     

             total used free shared buffers cached
    Mem: 15    12       3       0          0       8

    - buffers & cache 

    Mem  total used free

               15    4       11       



  • 7.  Re: How we can decrease memory utilization

    Posted 02-06-2018 03:04 AM

    Since you're either an employee or a contractor, you'll get a faster answer if you post on Yammer.



  • 8.  Re: How we can decrease memory utilization

    Posted 02-06-2018 03:16 AM

    We are contractor.Can you please ping me Yammer link.



  • 9.  Re: How we can decrease memory utilization

    Posted 02-06-2018 03:19 AM

    Send me an email from your CA email address.



  • 10.  Re: How we can decrease memory utilization

    Posted 02-06-2018 05:13 AM

    I am unable to send mail getting alerts like "you only send email to people who are following you"



  • 11.  Re: How we can decrease memory utilization

    Posted 02-06-2018 01:53 PM

    I asked that you please email me from your CA email address. If you have a CA email address you can find my name in the address book.