I don't like nifty or cool. It just over complicates things and makes things buggy.
10 is nothing like enought for a test. The JIT doesn't even kick in until you
thousands of repetitions. JITs are bettter at this than you could ever be and
will only get better over time.
View the original post :
Okay. I'm glad the VM is good at that. Like your JCA FAQ says, Are you *sure* you
want JCA?
Steve
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3831168#3831168
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3831168
It wouldn't even be testing what I thought it'd be testing. I wonder what the real
cutoff points are between
1. The VM developer
2. The Container developer
3. The container user (using JSP, other services on top of the container)
Anyways, I'll be quiet about things now :)
View the original
Very interesting.
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3831070#3831070
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3831070
---
This SF.Net email is sponsored
This was a single threaded test. Maybe it is different in multithreaded test.
Bill
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3831074#3831074
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3831074
Or if the Object is expensive to construct like a database connection.
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3831079#3831079
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3831079
Surely MultiThreaded would be worse (more contention)
unless your pooling uses a ThreadLocal pool
I removed all that crap from JBossMQ
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3831080#3831080
Reply to the post :
The test I did WAS using ThreadLocal as the pool. Object creation was still faster.
Maybe Object creation has a mutex and a multithreaded test would make regular object
creation slower than ThreadLocal.
Bill
View the original post :
I know yours was Bill.
Steve is interested in it in the context of a global pool:
http://www.jboss.org/index.html?module=bbop=viewtopict=48594
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3831092#3831092
Reply to the post :
What might be nifty is if the container could attempt to pool a resource. If the
container finds that one or the other is significantly faster, it could upgrade it to
a JCA, or downgrade it to no-pooling.
1. Get 10 objects using pool
2. Create 10 objects w/o pool
3. Compare the times.
4. AOP as
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3821210#3821210
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3821210
I have heard different things from different people. My thought was always that the
VM was better than
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3821223#3821223
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3821223
One more thing that will throw off HotSpot is the Advisable interface since it
essentially says that the
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3821232#3821232
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3821232
That's not the way JBoss AOP works. There will be no problem with HotSpot as you
describe.
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3821156#3821156
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3821156
Read an article today on HotSpot optimization that says basically the same thing you
said about object
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3820452#3820452
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3820452
That is kind of interesting really. People where bitching about the hit they were
taking with the object
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3820458#3820458
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3820458
I would say that this is because the MethodInvocations aren't hard referenced
for very long. The GC can
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3820390#3820390
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3820390
It is not costly to build Invocation objects (field, method, caller, etc...) as it is
only a bunch of
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3820392#3820392
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3820392
I thought object pooling was a good idea when creating the object was costly? If
creating
18 matches
Mail list logo
