Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Already on GitHub? Sign in to your account

Subscription messages drain slowly #9

Closed
jcookems opened this Issue Feb 6, 2013 · 5 comments

Comments

Projects
None yet
3 participants

jcookems commented Feb 6, 2013

Dev Estimate: 0
Test Estimate: 5

When running the chat app on my desktop computer, the subscription drains messages at a rate of 400 "messages" per minute. The actual number of end-user messages processed per minute is going to be even lower, because some fraction (75%?) of those messages are used by Socket.IO store for book-keeping.

That means that the number of chat messages processed per minute is going to be about 100, which sounds quite bad.

I believe that the throughput could be increased by asking the subscription for all available messages in a batch. But that option might only be available for Storage Queues :-(

jcookems commented Feb 6, 2013

Or perhaps the module should pre-batch the messages, and send chunkier, composite messages.

Contributor

christav commented Feb 12, 2013

I believe this was addressed by batching the sent messages.

It now behaves much better for huge storms of chat messages. I find (on my laptop) that 2000 chat messages get sent to all clients in about 20 seconds or so. (It is hard to tell exactly, but the SB subscriptions get emptied in under 30 seconds).

Owner

glennblock commented Feb 13, 2013

Excellent news!

On Tue, Feb 12, 2013 at 3:13 PM, Jason Cooke [Microsoft] <
notifications@github.com> wrote:

It now behaves much better for huge storms of chat messages. I find (on
my laptop) that 2000 chat messages get sent to all clients in about 20
seconds or so. (It is hard to tell exactly, but the SB subscriptions get
emptied in under 30 seconds).


Reply to this email directly or view it on GitHubhttps://github.com/WindowsAzure/socket.io-servicebus/issues/9#issuecomment-13465335.

Looks good.

@jcookems jcookems closed this Feb 18, 2013

christav added a commit that referenced this issue Mar 4, 2013

Merge pull request #9 from christav/use-sb-sequence-numbers-32
Using service bus managed sequences numbers instead of doing it ourselves.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment