[ https://issues.apache.org/jira/browse/FOP-2333?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14338196#comment-14338196 ]
Krishankant singh commented on FOP-2333: ---------------------------------------- We cached the Teamplates Object for this project and saw a dramatic reduction in CPU usage and it brought stability to the application as well. The CPU usage was halved after implementing this in production environment. Refer to- http://www.onjava.com/pub/a/oreilly/java/news/javaxslt_0801.html http://docstore.mik.ua/orelly/xml/jxslt/ch09_03.htm > knowing Multi threading issues for FOP 1.1 > ------------------------------------------ > > Key: FOP-2333 > URL: https://issues.apache.org/jira/browse/FOP-2333 > Project: Fop > Issue Type: Improvement > Components: unqualified > Affects Versions: 1.1 > Environment: Production > Reporter: Krishankant singh > Priority: Critical > Labels: performance > Fix For: 1.1 > > Original Estimate: 672h > Remaining Estimate: 672h > > Hi, > I am a software engineer - java/j2ee > We have a production application that creates 500 thousand pdf/day and it has > implemented fop 0.95 As per current implementation in our code, we have not > shared the FopFactory instance for threads. For each thread, we create a new > FopFactory instance, so after 6 or 7 days, the application CPU usage is too > high and the application needs to be restarted every 6 - 7 days. > As we know that creating new FopFactory instance for each thread is a very > costly operation, so to cater to above problem can we share one FopFactory > instance for all threads. Are there any problems reported with this approach > in fop 1.1 because we can for sure upgrade to fop 1.1 from fop 0.95 -- This message was sent by Atlassian JIRA (v6.3.4#6332)