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.

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

Update rate-limiting.md #7645

Merged
merged 3 commits into from
Jul 11, 2024
Merged

Update rate-limiting.md #7645

merged 3 commits into from
Jul 11, 2024

Conversation

sambellbraze
Copy link
Contributor

I've had a few customers recently submit support cases who wanted to understand the detailed workings of rate limits.

From my understanding, and reading a few SF KB articles, if you set the rate limit in Braze to be "10,000 messages per minute", Braze does NOT divide 10k by 60 seconds and then send 166 messages each second over the 60 second periods. Braze will send as many messages as possible as quickly as possible, but will NOT send more than 10,000 messages in a 60 second period.

This is due to a number of factors such a Connected Content... and if some calls fail or take longer to retrieve then Braze might not have sent those 166 messages and therefore needs to send more in the following seconds, which would break the "spread out the rate limit over 60 seconds perfectly evenly" rule".

However from working at Braze for 4.5yrs and speaking with customers... Every. Single. Customer. assumes the rate limit does split out the 10,000 messages evenly across the 60 second time period and so uses that calculation to determine their infrastructure capacity.

I felt it important to provide this insight in the docs hence my updates... if you think relevant.

Thanks!

Summary

My PR...

Related PRs, issues, or features (optional)

  • N/A

Feature release date (optional)

  • N/A

Contributor checklist

  • I confirm that my PR meets the following:
    • I signed the Contribution License Agreement (CLA).
    • My style and voice follows the Braze Style Guide.
    • My content contains correct spelling and grammar.
    • All links are working correctly.
    • If I renamed or moved a file or directory, I set up URL redirects for each file.
    • If I updated or replaced an image, I did not remove the original image file from the repository. (For more information, see Updating an image).
    • If my PR is related to a paid SKU, third party, SMS, AI, or privacy, I have received written approval from Braze Legal.

Submitting for review

If your PR meets the above requirements, select Ready for review, then add a reviewer:

  • Non-Braze contributors: Add braze-inc/docs-team as the reviewer.
  • Braze employees: Have any relevant subject matter experts (like engineers or product managers) review your work first, then add the tech writer assigned to your specific vertical. If you're not sure which tech writer to add, you can add braze-inc/docs-team instead.

Thanks for contributing! We look forward to reading your work.

I've had a few customers recently submit support cases who wanted to understand the detailed workings of rate limits. 

From my understanding, and reading a few SF KB articles, if you set the rate limit in Braze to be "10,000 messages per minute", Braze does NOT divide 10k by 60 seconds and then send 166 messages each second over the 60 second periods. Braze will send as many messages as possible as quickly as possible, but will NOT send more than 10,000 messages in a 60 second period. 

This is due to a number of factors such a Connected Content... and if some calls fail or take longer to retrieve then Braze might not have sent those 166 messages and therefore needs to send more in the following seconds, which would break the "spread out the rate limit over 60 seconds perfectly evenly" rule".

However from working at Braze for 4.5yrs and speaking with customers... Every. Single. Customer. assumes the rate limit does split out the 10,000 messages evenly across the 60 second time period and so uses that calculation to determine their infrastructure capacity. 

I felt it important to provide this insight in the docs hence my updates... if you think relevant.

Thanks!
@cla-bot cla-bot bot added the cla-signed label Jul 9, 2024
@lydia-xie lydia-xie self-requested a review July 11, 2024 21:11
@lydia-xie lydia-xie merged commit db5d558 into braze-inc:develop Jul 11, 2024
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants