Jordan / JP is MSMQ a protocol in the true sense of a protocol. or is it a "communication method".
I'm confused as I don't see MSMQ as a protocol (I wear LoadRunner blinkers as that's the only tool I have had exposure to, but I do have extensive experience in hands-on running of perf test environments (Web / UNIX / Mainframe and associated DB's and communication channels).
Is my limited experience of perf test tools clouding my understanding of a protocol?
MQ is an asynch message exchange and queueing service for between users, apps, systems or any combination thereof. There is a protocol hidden under the API used to communicate with it. I think it is OSI compliant and hides a lot of the lower layers (network, etc) from the implementer. So, it is both a service and it interfaces via protocol accessed via the API.
So, it would seem some of the performance concerns would be queue depth + winding and unwinding of it, and - number of MQ listeners.
What specifically are you looking for - how to, tools? A thought to factor into your response: There are many performance testing concepts/practices that apply to performance testing regardless of the service and/or protocol under test.
Bear in mind the original question was on MSMQ, not MQ.
I seem to recall MSMQ uses a variety of TCP and UDP ports for different aspects of its communications - including NetBios name services if I remember rightly. I've never tried performance testing it, but I have resorted to a packet sniffer for diagnosing Microsoft bugs (back in MSMQ 1.0 days), and from what I remember I'd say it would be an extremely difficult protocol to test with a tool that doesn't have native support.
Best bet would be to write custom scripts calling MSMQ functions at the API level if that is a possibility (rather then trying to handle the "on-the-wire" protocols).
None of which has much to do with the original question - testing a solution where requests are via MSMQ, responses via some other protocol. I presume that "other protocol" must be some other asynchronous messaging solution of some sort? I guess we need to know what the other protocol is and what speciific issues are being faced, to be able to shed any light.