What aspects of MSMQ performance would you like to know more about?

One thing that customers are short of is up-to-date information on MSMQ performance so they can plan for hardware requirements as their systems grow. I've tried to think what sort of data would be useful and have come up with the following short list:

  • Message type (Express vs Recoverable vs Transactional

  • Transaction scope (Single- vs Multi-message transaction; Internal vs External transaction)

  • Message size (Bytes vs Kbytes vs Mbytes)

  • Protocol (Classic vs Http vs Multicast)

  • Operations (Remote send vs Remote receive)

  • Architecture (32 bit vs 64 bit)

I don't think it is worth focussing on data from particular hardware as the results would be out of date in months.

Are there any other areas that could be investigated?

Comments (4)

  1. Chris says:

    What about the effect of DLQing

  2. MSDN Archive says:

    Hi Chris,

    There isn’t much activity when a message is moved to the Dead Letter Queue. A timer runs out and the location property of the message is changed from outgoing queue to dead letter queue so minimal disk I/O.

    Do you have a particular scenario in mind as having messages go to a DLQ isn’t what I’d think of as normal (i.e. healthy) activity.


    John Breakwell (MSFT)

  3. Mike Russell says:

    I’m interested in understanding for MSMQ (specifically MSMQ 3.0) total message capacity guidlines and what cpu/ram etc. is required for varying levels of performance.

  4. MSDN Archive says:

    Hi Mike,

    Unfortunately I’m still waiting on the product group to publish their performance white paper. The only public numbers are now VERY old (Windows NT4). I thought there was a white paper for Windows 2000 but can’t find the link at the moment:


    For discussions on machine capacity, these posts may help:



    This is definitely an area where there could be more guiadance customers.


    John Breakwell (MSFT)

Skip to main content