[
https://issues.apache.org/jira/browse/FREEMARKER-80?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16192658#comment-16192658
]
Daniel Dekany edited comment on FREEMARKER-80 at 10/5/17 9:20 AM:
------------------------------------------------------------------
Can you tell if and when can you test this? We are very close to starting the
2.3.27 release process (so this snapshot meant to be actually stable), so I
want to know if I should wait for this issue to resolve.
BTW, the snapshot release is also in the
https://repository.apache.org/content/repositories/snapshots/ Maven
repository with <version>2.3.27-incubating-SNAPSHOT</version>, in case that
makes things easier.
was (Author: ddekany):
Can you tell if and when can you test this? We are very close to starting the
2.3.27 release process (so this snapshot meant to be actually stable), so I
want to know if I should wait for this issue to resolve.
BTW, the snapshot release is also available is also in the
https://repository.apache.org/content/repositories/snapshots/ Maven
repository with <version>2.3.27-incubating-SNAPSHOT</version>, in case that
makes things easier.
> Performance bottleneck (from profiling)
> ---------------------------------------
>
> Key: FREEMARKER-80
> URL: https://issues.apache.org/jira/browse/FREEMARKER-80
> Project: Apache Freemarker
> Issue Type: Bug
> Components: engine
> Affects Versions: 2.3.26-incubating
> Environment: Linux, Java 8
> Reporter: Shevek
>
> Major performance bottleneck running on a 32-core system, limits effective
> number of threads to about 6: PropertyDescriptor.getReadMethod() is
> synchronized, and blocks other threads. Partial stack follows:
> java.beans.PropertyDescriptor.getReadMethod()
> BeanModel.invokeThroughDescriptor()
> BeanModel.get()
> Dot._eval()
> I suspect there's a workaround with using a method call directly in the FTL
> template, but I haven't figured it out yet. However, this is killing our
> performance. With Velocity, at the cost of a slower renderer, we can run all
> 32 cores, and get the job done faster.
> I'm not entirely sure how to figure out which piece of FTL is causing this
> stack.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
