Thanks for all of the great input! I did try sending non-persistent messages
as genman suggested and it increased the number of messages sent from 60 to
about 100, but that doesn't help me any since the application requires
persistent message handling. And adrian you made a good point about
Well, Gigabit ethernet would give you enough bandwidth, then you'll have to
look at faster disks, etc.
Out of curiosity, what is your application doing that requires so much
bandwidth? You might want to go with a hybrid approach where files are stored
in a content management system, and use
malmit wrote : Would JMS distributed destinations help
Hmm
I swamped my network so lets add more traffic to the network to implement
clustering.
Of course, this really depends upon your network topology and the quality of
the router. :-)
This is also another one of my favourite bug bears.
genman wrote : hybrid approach where files are stored in a content management
system, and use pointers to the files inside the message.
Exactly. It is even worse when you see people trying to propogate these
large messages through the jms chain of responsibility anti-pattern. :-)
View the
Probably the bottleneck you're running into is at the database (or
persistence) layer.
Why not the network? In a word bandwidth.
100 x 100KB = 10MB a second.
100Mbps Ethernet ~ 12MB a second
Even if all the packets were optimally filled, that doesn't include
* Other parts of the JMS protocol
The JBossMQ is backed using a messaging database. If this is slow (e.g. on a
slow disk), you're going to have slow JMS. Try testing with persistence turned
off, you should be see those numbers improve 10-100 times I'd imagine.
View the original post :
I don't think it is a bottleneck at the database. Just for testing purposes I
initialized my connection pool with 300 connections split up so that there are
3 nodes each with 100 connections. This I would imagine would be plenty of
connections. This set-up results in the 60 - 100KB
Probably the bottleneck you're running into is at the database (or persistence)
layer.
If you want to go with JBoss, you can use JBoss plus another messaging provider
pretty easily.
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3888970#3888970
Reply to the
