maximum message size #1205

Closed
ionelmoisuc opened this Issue Dec 24, 2012 · 6 comments

Comments

Projects
None yet
6 participants
@ionelmoisuc

Hello

What is the maximum message size that SignalR is meant to handle?

If client A sends a message split in chunks (a few messages) to a server and the server resends all those messages to client B, will client B receive messages in the same order as they were sent by client A ?

Thanks

@davidfowl

This comment has been minimized.

Show comment
Hide comment
@davidfowl

davidfowl Dec 24, 2012

Member
  1. There's no maximum message size but we recommend < 32K per message since they are being stored in a ring buffer (default size 5000). Storing larger messages will be awful for performance. See #1114 for details on how to handle large messages by chunking.
  2. Yes
Member

davidfowl commented Dec 24, 2012

  1. There's no maximum message size but we recommend < 32K per message since they are being stored in a ring buffer (default size 5000). Storing larger messages will be awful for performance. See #1114 for details on how to handle large messages by chunking.
  2. Yes

@davidfowl davidfowl closed this Dec 24, 2012

@mookid8000

This comment has been minimized.

Show comment
Hide comment
@mookid8000

mookid8000 Feb 12, 2014

Maybe it's me - but I'm seeing a maximum message size:
capture
with a funny (as in: "LOL - funneh!") error message:
capture2

The number of bytes actually transferred is slightly different than the numbers seen in the tests because the numbers in the tests is the size of a byte[] payload that I transfer in an envelope-type of object.

Is there something wrong with me?

Maybe it's me - but I'm seeing a maximum message size:
capture
with a funny (as in: "LOL - funneh!") error message:
capture2

The number of bytes actually transferred is slightly different than the numbers seen in the tests because the numbers in the tests is the size of a byte[] payload that I transfer in an envelope-type of object.

Is there something wrong with me?

@rayman7718

This comment has been minimized.

Show comment
Hide comment
@rayman7718

rayman7718 Sep 18, 2014

I'm seeing the same issue outlined above.
"There's no maximum message size but we recommend < 32K per message"
Well given that things don't work (and don't even provide a valid exception message) at a message size of >36864, there IS a maximum message size.

You recommend 32 K? why is that the limit, how is 32 K significant? Are we all supposed to send 8 bits around?

I'm seeing the same issue outlined above.
"There's no maximum message size but we recommend < 32K per message"
Well given that things don't work (and don't even provide a valid exception message) at a message size of >36864, there IS a maximum message size.

You recommend 32 K? why is that the limit, how is 32 K significant? Are we all supposed to send 8 bits around?

@gdefombelle

This comment has been minimized.

Show comment
Hide comment
@gdefombelle

gdefombelle Sep 25, 2014

limitation is 4Ko ;

limitation is 4Ko ;

@rayman7718

This comment has been minimized.

Show comment
Hide comment
@rayman7718

rayman7718 Sep 25, 2014

4Ko ??? You mean 4 KB? 40 KB ? 45 KB ?
Why is it useful ?

4Ko ??? You mean 4 KB? 40 KB ? 45 KB ?
Why is it useful ?

@Torvin

This comment has been minimized.

Show comment
Hide comment
@Torvin

Torvin Jun 9, 2016

@mookid8000 I think what you are seeing is a WebSocket size limit.

Torvin commented Jun 9, 2016

@mookid8000 I think what you are seeing is a WebSocket size limit.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment