NServiceBus与MSMQ相比性能较差

Question

We are trying to integrate NServiceBus/MSMQ in our current web application (REST).

Running the profiler, it seems that a lot of time is spent sending the message to the queue (see the profiler screen shot 1 , were the highlighted 30 is 30% of the overall execution time). It takes about twice the time just to send the message to MSMQ than saving an entire new set of documents in Mongo (running on a remote server).

Is it normal that sending a message to MSMQ queue is that slow or are we missing some configuration tweak?

The following is our current bus configuration (based on NServiceBus documentation - http://support.nservicebus.com/customer/portal/articles/894008-using-nservicebus-with-asp-net-mvc ):

// NServiceBus configuration
Configure
    .WithWeb()
    .CastleWindsorBuilder(_container)
    .JsonSerializer()
    .Log4Net()
    .MsmqTransport()
    .IsTransactional(false)
    .PurgeOnStartup(true)
    .UnicastBus()
    .ImpersonateSender(false)
    .SendOnly();

and web.config:

 <MessageForwardingInCaseOfFaultConfig ErrorQueue="Error" />
 <MsmqTransportConfig NumberOfWorkerThreads="1" MaxRetries="5" />
 <UnicastBusConfig>
   <MessageEndpointMappings>
     <add Messages="Messages" Endpoint="MessageHandlers" />
   </MessageEndpointMappings>
 </UnicastBusConfig>

Answer 1

This looks like an MSMQ issue . Transactional MSMQ simply isn't optimized for writing to it quickly.