Now I'm making the assumption that this is because the messages cannot be
transported to the destimation quick enough.
However the odd things are:
The source and destnation servers are right next to each other - both on the
same router
I tested thtoughput doing a big file FTP - it plenty
I tested round trip time using ping - no problem
AND it works find in my test lab - just not in production. In fact, the
transfer rate I can get in the test lab is 10 times what I'm getting in
production.
Non transacted private queue direct addressing.
Any ideas what I should be looking at?
If the queue is non-transactional and you are using Direct addressing then
messages should be flying.
What's the message size?
Have you selected authentication/encryption on the queue?
Check the Status of the queue and the Next Hop IP address in Computer
Management.
Using Performance Monitor, have a look at the "MSMQ Server" counters.
The "Outgoing messages/sec" and "MSMQ outgoing messages" counters should
give you an idea of how fast you are sending and also if there are any
breaks in transmission.
Also, how many messages already exist on the destination machine ("Total
bytes in all queues") and does this approach the machine quota?
Could be the messages can't be delivered because the other machine is nearly
full and has to wait for some delivered messages to be processed first.
Cheers
John Breakwell (MSFT)
"llama" <ll...@discussions.microsoft.com> wrote in message
news:97DEE292-A726-45EA...@microsoft.com...
In various lab setups I get 5000+ messages per second (~1000 byte messages)
On the production server I get at most 400 messages per second.
At the moment we are thinking its a problem with the switch ad that someow
the traffic is not getting routed fairly.
It seems that packets are being dropped which is not what one would expect.
So packet loss is causing the throughput to be very slow?
Note - just because a queue is empty doesn't mean the rest of MSMQ isn't
full. Dead letter and journal queues can sometimes be hidden stores of
messages if you enable them without monitoring them.
Cheers
John Breakwell (MSFT)
"llama" <ll...@discussions.microsoft.com> wrote in message
news:8B72942A-EE27-4093...@microsoft.com...