[
https://jira.jboss.org/browse/WELD-711?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12568910#comment-12568910
]
Martin Gencur commented on WELD-711:
------------------------------------
This commit (or series of commits) had crucial impact on performance, but the
bad way. The stress test now reaches only 4500 sessions while before it reached
10900 sessions. I compared these two builds: 1) weld/master with
head=7c9120c263 and 2) the WELD-711 branch from
https://github.com/pmuir/weld-core with head=610e3d977b, both were tested with
JSF 2.0. The resulting statistics are as follows:
https://hudson.qa.jboss.com/hudson/view/Weld/job/perf-weld-numberguess-stress-single/132/artifact/report/log.txt
,
https://hudson.qa.jboss.com/hudson/view/Weld/job/perf-weld-numberguess-stress-single/135/artifact/report/log.txt
> Calling Contextual.destroy on an instance still references an instance on
> BeanManager
> -------------------------------------------------------------------------------------
>
> Key: WELD-711
> URL: https://jira.jboss.org/browse/WELD-711
> Project: Weld
> Issue Type: Bug
> Components: Scopes & Contexts
> Affects Versions: 1.0.1.Final, 1.1.0.Beta1
> Reporter: George Gastaldi
> Assignee: Martin Gencur
> Priority: Minor
> Labels: AnnotationLiteral, MemoryLeak
> Fix For: 1.1.0.CR1
>
> Attachments: report.txt
>
>
> Using the seam-faces module @ViewScoped extension, when the object is
> destroyed by Contextual.destroy, weld still references an instance, avoiding
> being garbage-collected.
> Pseudo Code:
> Contextual contextual = ...
> Object instance = ...
> CreationalContext creational = ...
> contextual.destroy(instance, creational);
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
weld-issues mailing list
[email protected]
https://lists.jboss.org/mailman/listinfo/weld-issues
