Databases
StackOverflow2013
Postsdbo
PONServiceBus Pub/Sub Distributor/Worker Scenario Too Slow
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PONServiceBus Pub/Sub Distributor/Worker Scenario Too Slow
    primarykey
    data
    text
    <p>I am working on a proof of concept implementation of NServiceBus v4.x for work.</p> <p>Right now I have two subscribers and a single publisher. </p> <p>The publisher can publish over 500 message per second. It runs great.</p> <p>Subscriber A runs without distributors/workers. It is a single process.</p> <p>Subscriber B runs with a single distributor powering N number of workers. </p> <p>In my test I hit an endpoint that creates and publishes 100,000 messages. I do this publish with the subscribers off line.</p> <p>Subscriber A processes a steady 100 messages per second. Subscriber B with 2+ workers (same result with 2, 3, or 4) struggles to top 50 messages per second gross across all workers. </p> <p>It seems in my scenario that the workers (which I ramped up to 40 threads per worker) are waiting around for the distributor to give them work. </p> <p>Am I missing something possibly that is causing the distributor to be throttled? All Buses are running an unlimited Dev license.</p> <p>System Information: Intel Core i5 M520 @ 2.40 GHz 8 GBs of RAM SSD Hard Drive</p> <p><strong>UPDATE 08/06/2013</strong>: I finished deploying the system to a set of servers. I am experiencing the same results. Every server with a worker that I add decreases the performance of the subscriber.</p> <p>Subscriber B has a distributor on one server and two additional servers for workers. With Subscriber B and one server with an active worker I am experiencing ~80 messages/events per second. Adding in another worker on an additional physical machine decreases that to ~50 messages per second. Also, these are "dummy messages". No logic actually happens in the handlers other than a log of the message through log4net. Turning off the logging doesn't increase performance.</p> <p>Suggestions?</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USRyan M. Moore
    1. USRyan M. Moore
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    3. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. PONServiceBus Pub/Sub Distributor/Worker Scenario Too Slow
      1. This table or related slice is empty.
      1. VTUpMod
    1. This table or related slice is empty.
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload