[
https://issues.apache.org/jira/browse/CLEREZZA-320?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12919790#action_12919790
]
Tsuyoshi Ito edited comment on CLEREZZA-320 at 10/11/10 6:57 AM:
-----------------------------------------------------------------
tested on an demoserver (linux, quad-core, 8GB RAM):
A page executes 20x render(...) and consists of 8-10 ssp renderlets
200 concurrent users (10 sec click delay) average respone time 160ms (see
attachement)
was (Author: tsuy):
tested on an demoserver (linux, quad-core, 8GB RAM):
200 concurrent users (10 sec click delay) average respone time 160ms (see
attachement)
> SSP rendering is slow:
> scala.tool.nsc.interpreter.AbstractFileClassLoader.findClass needs a lot of
> time to be executed
> -----------------------------------------------------------------------------------------------------------------------
>
> Key: CLEREZZA-320
> URL: https://issues.apache.org/jira/browse/CLEREZZA-320
> Project: Clerezza
> Issue Type: Bug
> Environment: in netbeans, during cpu profiling exclude all java core
> classes
> Reporter: Tsuyoshi Ito
> Assignee: Reto Bachmann-Gmür
> Priority: Blocker
> Attachments: org.clerezza.test.render.zip,
> page_reuest_wo_javacore.png, stresstest-200users.png
>
>
> during profiling session we detected that rendering ssp is very slow. A lot
> of time is used to execute
> scala.tool.nsc.interpreter.AbstractFileClassLoader.findClass. Seems that each
> execution the classes are (re)loaded. IMO this should not be the case.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
