Skip to content
New issue

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

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Document any and all limits #53

Closed
mattheworiordan opened this issue Oct 13, 2015 · 2 comments
Closed

Document any and all limits #53

mattheworiordan opened this issue Oct 13, 2015 · 2 comments
Assignees
@m-hulbert
Labels
api-reference Anything that appears below the API reference blue fold content-request A request for new content, as opposed to changing/fixing existing content medium Expected to take up to 1 week no-sync Do not sync ticket to JIRA priority-p2 Need to complete in current quarter

Comments

@mattheworiordan
Copy link
Member

mattheworiordan commented Oct 13, 2015 •
edited by ably-sync-bot
Loading

For example, how long we retain messages when a connection is dropped, or how many messages can be retained by the connection state on a frontend, total messages per second, message size etc.

┆Issue is synchronized with this Jira Task by Unito
@mattheworiordan mattheworiordan added the content-request A request for new content, as opposed to changing/fixing existing content label Oct 13, 2015
@mattheworiordan
Copy link
Member Author

Include recommendations in regards to concurrency, especially in regards to REST requests and our recommendation to use a Realtime connection instead, perhaps more than 100 concurrent connections should use a Realtime connection

@mattheworiordan mattheworiordan added this to the website 1.0 milestone Jan 21, 2016
@mattheworiordan mattheworiordan added the api-reference Anything that appears below the API reference blue fold label Jan 21, 2016
@mattheworiordan
Copy link
Member Author

This is covered in https://support.ably.io/solution/articles/3000053845-do-you-have-any-connection-message-rate-or-other-limits-on-accounts-, but we should consider this in the docs too, at least a link

@mattheworiordan mattheworiordan modified the milestones: website 1.0, queue docs Jan 18, 2017
@MarkWoulfeAbly MarkWoulfeAbly added the no-sync Do not sync ticket to JIRA label Sep 2, 2020
@tbedford tbedford added medium Expected to take up to 1 week priority-p2 Need to complete in current quarter Q2-2021 labels Mar 30, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@m-hulbert m-hulbert

Labels
api-reference Anything that appears below the API reference blue fold content-request A request for new content, as opposed to changing/fixing existing content medium Expected to take up to 1 week no-sync Do not sync ticket to JIRA priority-p2 Need to complete in current quarter
Milestone
No milestone
Development

No branches or pull requests
5 participants
@mattheworiordan @tbedford @m-hulbert @MarkWoulfeAbly @ably-sync-bot