May 2008 - jboss-dev-forums - Jboss List Archives

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: Scaling UP tests

by clebert.suconic＠jboss.com

Another thing.. about the 300 msg/second with NIO. I have a SCSI (or as they call it now.. SAS) disk... and that is very fast at write, and it seems slow at sync. That's why I got this rate of 350 messages / second. On the laptop I got about 1000 messages / second. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4153107#4153107 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4153107

18 years

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: Scaling UP tests

by clebert.suconic＠jboss.com

As we have talked on the IRC, there is a task to improve concurrency on QueueImpl. Running the test with a single Sender and a single Listener was okay. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4153106#4153106 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4153106

18 years

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: Scaling UP tests

by clebert.suconic＠jboss.com

to complete the thread: 5 perfSenders running as: ant -Ddelivery.mode=PERSISTENT -Dsess.trans=false perfSender and 1 perfListener running as: ant -Dsess.trans=true -Dsess.trans.size=1000 -Dmessage.count=1000000 perfListener That is... 5 non Transactioned sender.. and 1 transactioned receiver. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4153097#4153097 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4153097

18 years

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Scaling UP tests

by clebert.suconic＠jboss.com

I have been trying to scale up few tests with nonTransactionSends/Persistent (that means.. every send requires transaction), and this scaled pretty nicely with AIO. With NIO I've got about 350 sends / second with a single perfSender, because of the syncs on every send. With AIO I've got 1200 sends /s econd with a single perfSender. I've also tested with 5 perfSender, and I've got the same rate on every perfSender. That means.. it scaled without any problem. *However* when I added a listener, things were much different. The rate on the send was terrible, and I got a bunch of threads waiting on this condition: | [java] "pool-7-thread-4" prio=1 tid=0x00007fb8e96d56c0 nid=0x3d44 waiting for monitor entry [0x000000004396f000..0x000000004396fb20] | [java] at org.jboss.messaging.core.server.impl.QueueImpl.addLast(QueueImpl.java:159) | [java] - waiting to lock <0x00007fb8f0a62968> (a org.jboss.messaging.core.server.impl.QueueImpl) | [java] at org.jboss.messaging.core.server.impl.ServerSessionImpl.send(ServerSessionImpl.java:321) | [java] at org.jboss.messaging.core.server.impl.ServerProducerImpl.send(ServerProducerImpl.java:103) | [java] at org.jboss.messaging.core.server.impl.ServerProducerPacketHandler.doHandle(ServerProducerPacketHandler.java:61) | [java] at org.jboss.messaging.core.server.impl.ServerPacketHandlerSupport.handle(ServerPacketHandlerSupport.java:48) | [java] at org.jboss.messaging.core.remoting.impl.PacketDispatcherImpl.dispatch(PacketDispatcherImpl.java:139) | [java] at org.jboss.messaging.core.remoting.impl.mina.MinaHandler.messageReceivedInternal(MinaHandler.java:283) | [java] at org.jboss.messaging.core.remoting.impl.mina.MinaHandler.access$000(MinaHandler.java:32) | [java] at org.jboss.messaging.core.remoting.impl.mina.MinaHandler$1.run(MinaHandler.java:165) | [java] at org.jboss.messaging.util.OrderedExecutorFactory$ChildExecutor.run(OrderedExecutorFactory.java:70) | [java] at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650) | [java] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675) | [java] at java.lang.Thread.run(Thread.java:595) | [java] | While this thread was holding the lock: [java] "pool-7-thread-1" prio=1 tid=0x00007fb8e9870bc0 nid=0x3d33 in Object.wait() [0x00000000413a4000..0x00000000413a4da0] | [java] at java.lang.Object.wait(Native Method) | [java] - waiting on <0x00007fb8f09b0528> (a org.jboss.messaging.core.remoting.impl.mina.MinaHandler) | [java] at org.jboss.messaging.core.remoting.impl.mina.MinaHandler.checkWrite(MinaHandler.java:210) | [java] - locked <0x00007fb8f09b0528> (a org.jboss.messaging.core.remoting.impl.mina.MinaHandler) | [java] at org.jboss.messaging.core.remoting.impl.mina.MinaHandler$2.send(MinaHandler.java:251) | [java] at org.jboss.messaging.core.server.impl.DeliveryImpl.deliver(DeliveryImpl.java:80) | [java] at org.jboss.messaging.core.server.impl.ServerSessionImpl.handleDelivery(ServerSessionImpl.java:222) | [java] at org.jboss.messaging.core.server.impl.ServerConsumerImpl.handle(ServerConsumerImpl.java:217) | [java] - locked <0x00007fb8f0a62a90> (a java.lang.Object) | [java] at org.jboss.messaging.core.server.impl.QueueImpl.deliver(QueueImpl.java:631) | [java] at org.jboss.messaging.core.server.impl.QueueImpl.add(QueueImpl.java:528) | [java] at org.jboss.messaging.core.server.impl.QueueImpl.addLast(QueueImpl.java:159) | [java] - locked <0x00007fb8f0a62968> (a org.jboss.messaging.core.server.impl.QueueImpl) | [java] at org.jboss.messaging.core.server.impl.ServerSessionImpl.send(ServerSessionImpl.java:321) | [java] at org.jboss.messaging.core.server.impl.ServerProducerImpl.send(ServerProducerImpl.java:103) | [java] at org.jboss.messaging.core.server.impl.ServerProducerPacketHandler.doHandle(ServerProducerPacketHandler.java:61) | [java] at org.jboss.messaging.core.server.impl.ServerPacketHandlerSupport.handle(ServerPacketHandlerSupport.java:48) | [java] at org.jboss.messaging.core.remoting.impl.PacketDispatcherImpl.dispatch(PacketDispatcherImpl.java:139) | [java] at org.jboss.messaging.core.remoting.impl.mina.MinaHandler.messageReceivedInternal(MinaHandler.java:283) | [java] at org.jboss.messaging.core.remoting.impl.mina.MinaHandler.access$000(MinaHandler.java:32) | [java] at org.jboss.messaging.core.remoting.impl.mina.MinaHandler$1.run(MinaHandler.java:165) | [java] at org.jboss.messaging.util.OrderedExecutorFactory$ChildExecutor.run(OrderedExecutorFactory.java:70) | [java] at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650) | [java] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675) | [java] at java.lang.Thread.run(Thread.java:595) | [java] | I haven't taken any conclusions about what's wrong as I haven't looked on the code yet. These are just figures from my test. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4153096#4153096 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4153096

18 years

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: Multiple parsing implementation in RARDeployer

by alesj

"vickyk" wrote : | Yes but I am not sure if this would work as I understand that the SRD will not work unless SchemaResoverFactory is also updated. | Let me have a look at you tests. | I'll make it work. ;) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4153081#4153081 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4153081

18 years

1
0
0 / 0

[Design of EJB 3.0] - Re: Validation of Complete EJB2.x Views: EJB3 or Metadata?

by wolfc

I'm assuming that 'someValidator' is a facade for all validations. :-) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4153074#4153074 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4153074

18 years

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: Multiple parsing implementation in RARDeployer

by vickyk

"alesj" wrote : | The problem that I see is that SRDeployer is expecting single output type (in test's case it's KernelDeloyment), where we actually need different types out of parse method, and combine them in merge function. | Yes but I am not sure if this would work as I understand that the SRD will not work unless SchemaResoverFactory is also updated. Let me have a look at you tests . View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4153072#4153072 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4153072

18 years

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: Multiple parsing implementation in RARDeployer

by vickyk

"vickyk" wrote : | I am yet not sure if I need OMFD or SRD , any thoughts ? Ok looks like the SRD will not be used unless the SchemaResolverFactory is updated as shown in this diff http://viewvc.jboss.org/cgi-bin/viewvc.cgi/common/jbossxb/trunk/src/main/... Let me investigate more options . View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4153071#4153071 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4153071

18 years

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Where does runServer log too

by timfox

I was trying to figure out where the log gets written to when ant runSender is run... any ideas? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4153067#4153067 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4153067

18 years

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: Multiple parsing implementation in RARDeployer

by alesj

"vickyk" wrote : | How can I do that ? | Currently there is no elegant solution. :-) The problem that I see is that SRDeployer is expecting single output type (in test's case it's KernelDeloyment), where we actually need different types out of parse method, and combine them in merge function. "vickyk" wrote : | I am yet not sure if I need OMFD or SRD , any thoughts ? | I'll prepare you a proper multi-input-type/single-output-type parser/deployer, along with the tests over the weekend. ;-) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4153065#4153065 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4153065

18 years

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-dev-forums May 2008