Formed in 2009, the Archive Team (not to be confused with the archive.org Archive-It Team) is a rogue archivist collective dedicated to saving copies of rapidly dying or deleted websites for the sake of history and digital heritage. The group is 100% composed of volunteers and interested parties, and has expanded into a large amount of related projects for saving online and digital history.
Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.
Sign upIncease maxPayloadLength upper limit and/or allow 0 (limitless) #382
Comments
|
If you want to transfer hundreds of GB you really shouldn't use one single WebSocket message. Use streaming HTTP and you can cut your memory usage in half at least? |
|
@alexhultman what
|
|
Docs for maxPayloadLength say per message
|
|
Thanks for the pointer @hst-m |
|
@alexhultman our service is Anyway, i can close the issue. Thanks guys |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
My uWebSockets.js app daily handles large amount of data (
10-35GBper conn) with no issue.One of my colleagues tried to increase the
maxPayloadLengthto100GBfor stress testing but it didn't work. Apparently, there's a50GBupper bound limit.Is there any reason for that?
@alexhultman two suggestions if you don't mind:
maxPayloadLengthto take value0(no limit) and let the user handle the limit logic on his sidemaxPayloadLengthto a much larger value: for example100TB(see websocket-frame-size-limitation)