You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/service-bus-messaging/service-bus-performance-improvements.md
-12Lines changed: 0 additions & 12 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -298,8 +298,6 @@ Goal: Maximize the throughput of a single queue. The number of senders and recei
298
298
299
299
* To increase the overall send rate into the queue, use multiple message factories to create senders. For each sender, use asynchronous operations or multiple threads.
300
300
* To increase the overall receive rate from the queue, use multiple message factories to create receivers.
301
-
* Use asynchronous operations to take advantage of client-side batching.
302
-
* Leave batched store access enabled. This access increases the overall rate at which messages can be written into the queue.
303
301
* Set the prefetch count to 20 times the maximum processing rates of all receivers of a factory. This count reduces the number of Service Bus client protocol transmissions.
304
302
305
303
### Multiple high-throughput queues
@@ -312,8 +310,6 @@ To obtain maximum throughput across multiple queues, use the settings outlined t
312
310
313
311
Goal: Minimize latency of a queue or topic. The number of senders and receivers is small. The throughput of the queue is small or moderate.
314
312
315
-
* Disable client-side batching. The client immediately sends a message.
316
-
* Disable batched store access. The service immediately writes the message to the store.
317
313
* If using a single client, set the prefetch count to 20 times the processing rate of the receiver. If multiple messages arrive at the queue at the same time, the Service Bus client protocol transmits them all at the same time. When the client receives the next message, that message is already in the local cache. The cache should be small.
318
314
* If using multiple clients, set the prefetch count to 0. By setting the count, the second client can receive the second message while the first client is still processing the first message.
319
315
@@ -326,8 +322,6 @@ Service Bus enables up to 1,000 concurrent connections to a messaging entity. Th
326
322
To maximize throughput, follow these steps:
327
323
328
324
* If each sender is in a different process, use only a single factory per process.
329
-
* Use asynchronous operations to take advantage of client-side batching.
330
-
* Leave batched store access enabled. This access increases the overall rate at which messages can be written into the queue or topic.
331
325
* Set the prefetch count to 20 times the maximum processing rates of all receivers of a factory. This count reduces the number of Service Bus client protocol transmissions.
332
326
333
327
### Queue with a large number of receivers
@@ -339,8 +333,6 @@ Service Bus enables up to 1,000 concurrent connections to an entity. If a queue
339
333
To maximize throughput, follow these guidelines:
340
334
341
335
* If each receiver is in a different process, use only a single factory per process.
342
-
* Receivers can use synchronous or asynchronous operations. Given the moderate receive rate of an individual receiver, client-side batching of a Complete request doesn't affect receiver throughput.
343
-
* Leave batched store access enabled. This access reduces the overall load of the entity. It also increases the overall rate at which messages can be written into the queue or topic.
344
336
* Set the prefetch count to a small value (for example, PrefetchCount = 10). This count prevents receivers from being idle while other receivers have large numbers of messages cached.
345
337
346
338
### Topic with a few subscriptions
@@ -351,8 +343,6 @@ To maximize throughput, follow these guidelines:
351
343
352
344
* To increase the overall send rate into the topic, use multiple message factories to create senders. For each sender, use asynchronous operations or multiple threads.
353
345
* To increase the overall receive rate from a subscription, use multiple message factories to create receivers. For each receiver, use asynchronous operations or multiple threads.
354
-
* Use asynchronous operations to take advantage of client-side batching.
355
-
* Leave batched store access enabled. This access increases the overall rate at which messages can be written into the topic.
356
346
* Set the prefetch count to 20 times the maximum processing rates of all receivers of a factory. This count reduces the number of Service Bus client protocol transmissions.
357
347
358
348
### Topic with a large number of subscriptions
@@ -363,6 +353,4 @@ Topics with a large number of subscriptions typically expose a low overall throu
363
353
364
354
To maximize throughput, try the following steps:
365
355
366
-
* Use asynchronous operations to take advantage of client-side batching.
367
-
* Leave batched store access enabled. This access increases the overall rate at which messages can be written into the topic.
368
356
* Set the prefetch count to 20 times the expected rate at which messages are received. This count reduces the number of Service Bus client protocol transmissions.
0 commit comments