This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

iPrint process consumes a lot of memory, normal?

Hey guys,

the iPrint Advanced installation on our OES 2018SP3 consumes a lot of memory... Is that normal? We are running around 20 printers, on 100 Workstations with 150 users...

This is top sorted with memory consumtion... 

Any ideas where to check?

Thanks in advance

Parents
  • 0  
  • 0 in reply to   

    Hello Gonzalo,

    thanks for your reply...

    Its sounds to fit perfectly for my problem but unfortunatly, the properties section is already there with the given entries... Any other ideas? 

  • 0   in reply to 

    then it could be normal. java is a heavy beast. What do you get with this command:

    ps -eo pmem, pcpu,pid,user,args | sort -k 1 -r | head -15

  • 0 in reply to   

    Sure, there you go...

    %MEM %CPU   PID USER     COMMAND
     1.3  0.0  3962 iprintm+ /usr/lib64/jvm/jre-1.8.0-openjdk/bin/java -Xmx512m -XX:MaxMetaspaceSize=512m -classpath /var/opt/novell/iprint-tomcat/bin/bootstrap.jar:/var/opt/novell/iprint-tomcat/bin/tomcat-juli.jar:/usr/share/java/commons-daemon.jar -Dcatalina.base=/var/opt/novell/iprint-tomcat -Dcatalina.home=/var/opt/novell/iprint-tomcat -Djava.endorsed.dirs= -Djava.io.tmpdir=/var/opt/novell/iprint-tomcat/temp -Djava.util.logging.config.file=/var/opt/novell/iprint-tomcat/conf/logging.properties -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager org.apache.catalina.startup.Bootstrap start
     1.2  0.0  1353 iprint   /usr/bin/java -jar /opt/novell/iprintlicense/lib/license-launcher-0.0.1-SNAPSHOT.jar
     1.1  0.0  1978 iprint   /usr/bin/java -Xmx512m -XX:MaxMetaspaceSize=512m -cp /opt/novell/iprintauth/lib/iprint-auth-launcher-*.jar:/opt/novell/iprintauth/lib/* com.microfocus.service.iprint.auth.application.MainApplication
     1.0  1.1  1472 root     //opt/novell/eDirectory/sbin/ndsd
     0.8  0.4  1324 iprintm+ java -server -Xmx1G -XX:MaxMetaspaceSize=1G -Djna.nosys=true -XX:+HeapDumpOnOutOfMemoryError -Djava.awt.headless=true -Dfile.encoding=UTF8 -Drhino.opt.level=9 -Denvironment.dumpCfgAtStartup=true -Dtx.useLog=false -Djava.util.logging.manager=com.orientechnologies.common.log.ShutdownLogManager -Djava.util.logging.config.file=/usr/share/orientdb/config/orientdb-server-log.properties -Dorientdb.config.file=/usr/share/orientdb/config/orientdb-server-config.xml -Dorientdb.www.path=/usr/share/orientdb/www -Dorientdb.build.number=3.0.x@r355adf5e012545012ea2ef7682bcb95f77b0934e; 2020-03-18 15:14:21+0000 -cp /usr/share/orientdb/lib/orientdb-server-3.0.30.jar:/usr/share/orientdb/lib/*:/usr/share/orientdb/plugins/* com.orientechnologies.orient.server.OServerMain
     0.7  0.3  1474 named    /usr/sbin/named -t /var/lib/named -u named
     0.5  0.0  1651 wwwrun   /usr/lib64/jvm/jre-1.8.0-ibm/bin/java -Djava.library.path=/opt/novell/eDirectory/lib64:/var/opt/novell/tomcat/lib:/usr/lib64:/opt/novell/lib64:/var/opt/novell/iManager/nps/WEB-INF/bin/linux -Dorg.apache.jasper.compiler.Parser.STRICT_QUOTE_ESCAPING=false -Dorg.apache.catalina.STRICT_SERVLET_COMPLIANCE=false -Dorg.apache.jasper.compiler.Parser.STRICT_WHITESPACE=false -Dorg.apache.tomcat.util.http.ServerCookie.FWD_SLASH_IS_SEPARATOR=false -Djdk.tls.ephemeralDHKeySize=2048 -classpath /usr/share/tomcat/bin/bootstrap.jar:/usr/share/tomcat/bin/tomcat-juli.jar:/usr/share/java/commons-daemon.jar -Dcatalina.base=/var/opt/novell/tomcat -Dcatalina.home=/var/opt/novell/tomcat -Djava.endorsed.dirs= -Djava.io.tmpdir=/var/opt/novell/tomcat/temp -Djava.util.logging.config.file=/etc/opt/novell/tomcat/conf/logging.properties -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager org.apache.catalina.startup.Bootstrap start
     0.4  0.1  8908 squid    (squid-1) --kid squid-1 -FC
     0.3  0.0  1321 root     /opt/paedML/skmobil/jre/bin/java -jar /opt/paedML/skmobil/backend.jar -Dspring.config.additional-location=/opt/paedML/skmobil/config
     0.0  0.3  3904 root     /opt/novell/nss/sbin/jstcpd
     0.0  0.2 23980 root     /opt/novell/iprint/bin/iprintgw
     0.0  0.1  5489 root     /opt/novell/afptcpd/bin/afptcpd
     0.0  0.1  3171 root     /opt/novell/ncl/bin/novfsd
     0.0  0.1  2802 novlxsr+ /opt/novell/xtier/bin/novell-xsrvd -d

  • 0   in reply to 

    looks normal

  • 0 in reply to   

    So i'll add couple more gigs of ram and watch it?

  • 0   in reply to 

    i do not see any problem with your server. Not sure why you want to add more memory. 

  • 0   in reply to 

    Why are you doing that?  To what end?  Is there a problem you haven't told us about?

    It isn't like your swap is getting consumed much at all, and that is what I usually use as my driver for if more RAM is needed.  A common part of my health check is the 'free -m' command, and as long as swap stays well under half used, I don't worry about memory usage unless something else strongly points to it.  Using lots of a plentiful resource is not a reason to just add more.

    ________________________

    Andy of KonecnyConsulting.ca in Toronto
    Please use the "Like" and/or "Verified Answers" as appropriate as that helps us all.

Reply
  • 0   in reply to 

    Why are you doing that?  To what end?  Is there a problem you haven't told us about?

    It isn't like your swap is getting consumed much at all, and that is what I usually use as my driver for if more RAM is needed.  A common part of my health check is the 'free -m' command, and as long as swap stays well under half used, I don't worry about memory usage unless something else strongly points to it.  Using lots of a plentiful resource is not a reason to just add more.

    ________________________

    Andy of KonecnyConsulting.ca in Toronto
    Please use the "Like" and/or "Verified Answers" as appropriate as that helps us all.

Children
  • 0 in reply to   

    Because the server acts snappy when MEM free runs low... Also the server is quite old and running on HDDs, so swapping is really slow...

  • 0   in reply to 
    snappy

    Normally snappy implies fast and quickly responding, perhaps too fast.  I suspect that wasn't what you were trying to say from the tone of the rest of what you wrote.

    For an iPrint only server, the question is what humanly perceivable performance issues are there that can be directly attributed to the server?  Also would be worth checking the drive system to make sure it doesn't have any issues (such as a drive down) as all print jobs do get written to disk as part of printing, so any slow-downs there would be a notable impact way beyond anything those memory numbers you shared would indicate.

    Have you used ganglia to see the memory trends?  http://serverIP/gweb   

    I have a client of about the same size, with their iPrint vm working just fine with 4GB of ram, even with the charge-back mechanisms in place.

    ________________________

    Andy of KonecnyConsulting.ca in Toronto
    Please use the "Like" and/or "Verified Answers" as appropriate as that helps us all.

  • 0 in reply to   

    Hey Andy,

    lol Joy, no that wasnt what i ment and thanks for clearing that up. Now it makes totally sense that other people reacts weird when i used the word like i did...

    Its not an iPrint only server... Its the main server hosting NDS, NSS, DHCP, DNS, LDAP and iPrint Advanced...

    I didnt check the ganglia service but i will...

    I think i will move the iPrint Service to its own appliance