Re: [weld-dev] [cdi-dev] microbenchmark for CDI performance
by Jozef Hartinger
Btw I've run your benchmark locally and observed the following results:
OWB 1.2.6: 9827ms
Weld 2.2.5.Final: 20ms
;-)
I did however tweak the test a bit so that Weld's optimizations can be
leveraged[1]. I admit that in certain situations (like your test without
my change) Weld performs worse than it should and this is a good input
for us.
As for the NPE you observed not sure what is going on there. Perhaps
WeldContextControl implementation in DeltaSpike is not really thread safe?
Jozef
[1] https://github.com/jharting/cdi-performance/commits/weld
On 10/21/2014 01:43 PM, Jozef Hartinger wrote:
> Hi Mark,
>
> thanks for showcasting your new feature. Great to see OWB getting
> faster! As for the micro benchmark I suggest that you check out JMH[1].
>
> If you need an input from the Weld team, use weld-dev(a)lists.jboss.org
>
> [1] http://openjdk.java.net/projects/code-tools/jmh/
>
> On 10/21/2014 11:59 AM, Mark Struberg wrote:
>> Hi!
>>
>> Weld folks, I need some help with a micro benchmark:
>>
>> You know we've talked about disk footprint in SE, so I hacked together a small microbenchmark and as a side effect we also got what is really needed to have CDI running
>>
>> https://github.com/struberg/cdi-performance
>>
>> I'm curious about missing some dependency excludes for Weld.
>>
>> could you please run
>>
>> $> mvn clean dependency:copy-dependencies -DincludeScope=compile -PWeld -Dweld.version=2.2.5.Final
>> $> ls -al target/dependency/
>>
>> and tell me which dependencies can be without having some CDI functionality missing?
>>
>> Feel free to pimp the pom and ship a pull request.
>>
>>
>> txs and LieGrue,
>> strub
>> _______________________________________________
>> cdi-dev mailing list
>> cdi-dev(a)lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/cdi-dev
>>
>> Note that for all code provided on this list, the provider licenses the code under the Apache License, Version 2 (http://www.apache.org/licenses/LICENSE-2.0.html). For all other ideas provided on this list, the provider waives all patent and other intellectual property rights inherent in such information.
> _______________________________________________
> cdi-dev mailing list
> cdi-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/cdi-dev
>
> Note that for all code provided on this list, the provider licenses the code under the Apache License, Version 2 (http://www.apache.org/licenses/LICENSE-2.0.html). For all other ideas provided on this list, the provider waives all patent and other intellectual property rights inherent in such information.
8 years, 9 months
Re: [weld-dev] [cdi-dev] microbenchmark for CDI performance
by Mark Struberg
I was under the impression that weld-dev just got renamed to cdi-dev.
I also got another issue while quickly starting up new threads:
88 [main] INFO org.jboss.weld.Bootstrap - WELD-000101 Transactional services not available. Injection of @Inject UserTransaction not available. Transactional observers will be invoked synchronously.
Exception in thread "Thread-3" java.lang.NullPointerException
at org.apache.deltaspike.cdise.weld.ContextController.startRequestScope(ContextController.java:147)
at org.apache.deltaspike.cdise.weld.WeldContextControl.startRequestScope(WeldContextControl.java:161)
at org.apache.deltaspike.cdise.weld.WeldContextControl.startContext(WeldContextControl.java:70)
at at.struct.cdi.performance.CdiPerformanceTest$1.run(CdiPerformanceTest.java:56)
at java.lang.Thread.run(Thread.java:745)
is this a concurrency issue under high load? Or am I just doing something wrong?
LieGrue,
strub
On Tuesday, 21 October 2014, 12:49, John D. Ament <john.d.ament(a)gmail.com> wrote:
>
>
>Mark,
>
>
>Did you mean to send this to weld-dev instead of cdi-dev? (though I'm not sure if that list is still maintained)
>
>
>At first glance, these look odd:
>
>
>persistence-api-1.0.2.jar
>validation-api-1.0.0.GA.jar
>jboss-ejb-api_3.1_spec-1.0.2.Final.jar
>jboss-el-api_3.0_spec-1.0.0.Alpha1.jar
>
>
>I don't recall them coming in when running SE.
>
>
>On Tue, Oct 21, 2014 at 5:59 AM, Mark Struberg <struberg(a)yahoo.de> wrote:
>
>Hi!
>>
>>Weld folks, I need some help with a micro benchmark:
>>
>>You know we've talked about disk footprint in SE, so I hacked together a small microbenchmark and as a side effect we also got what is really needed to have CDI running
>>
>>https://github.com/struberg/cdi-performance
>>
>>I'm curious about missing some dependency excludes for Weld.
>>
>>could you please run
>>
>>$> mvn clean dependency:copy-dependencies -DincludeScope=compile -PWeld -Dweld.version=2.2.5.Final
>>$> ls -al target/dependency/
>>
>>and tell me which dependencies can be without having some CDI functionality missing?
>>
>>Feel free to pimp the pom and ship a pull request.
>>
>>
>>txs and LieGrue,
>>strub
>>_______________________________________________
>>cdi-dev mailing list
>>cdi-dev(a)lists.jboss.org
>>https://lists.jboss.org/mailman/listinfo/cdi-dev
>>
>>Note that for all code provided on this list, the provider licenses the code under the Apache License, Version 2 (http://www.apache.org/licenses/LICENSE-2.0.html). For all other ideas provided on this list, the provider waives all patent and other intellectual property rights inherent in such information.
>>
>
>
>
8 years, 11 months