Being throttled meaning2/28/2023 ![]() Not only because it does not need to scale up (it is only itself) but also It’s virtually free for your client application to wait. Advantage of Letting the Client Handle Throttling It’s also different for your server-side application, which might receive thousands of calls per second and can also not handle the extra resource consumption. It’s different for the cloud database, which may have millions of calls per second and cannot handle using 200 times too many resources. This puts the wait time on your client application, and whether that is a browser or another client, it will not be impacted greatly by having to wait a bit longer. Your client application can also be built to receive and understand that it has been throttled and retry. Well, you have someone to pass the cost on to as well - the client applicationĢ. Clever how the cloud database passed their problems on to you, right? Using this option means that your application will spend that time and those resources waiting for the cloud database. Cosmos DB will even respond with a header that tells you how long to wait before you should try again. In your server-side application, catch the throttling status code (usually 429 or 503), wait for a second or two, and then call again. Happen, and you can make a conscious choice about how it happens:ġ. So instead, they will respond immediately and tell you to call later.Īs throttling is “normal,” you need to be ready for it to We have already established that time is money and that theĬloud database provider does not want to spend that time and money on their end, Infrastructure, so if you use up significant resources, then fewer resourcesĪre available for others, and their calls would hang as well, creating a So, another way to look at this is that throttling makes ![]() ![]() More expensive than using 1 KB of memory for 1 second. Time is money and using 1 KB of memory for 10 seconds is 10 times Network connections and memory for a call 200 times longer. Imagine if instead of 50 milliseconds, a call took 10 For both Cosmos DB and our own Gyxiĭatabase, calls consistently take less than 50 milliseconds. So why, when using a cloud database, do you have to get used When you are used to an old school database server, you areĪlso used to incredible robustness. In short, throttling means you are exceeding your capacityĪnd to call back later. You reserved, it will also be fast to tell you that. Cosmos DB is always fast, and if you exceed the capacity For example, Cosmos DB sells capacity in chunks of 100 Request Units, and if you exceed that, you are throttled.Ĭloud databases do this in order to offer you predictableĪnd fast performance. Throttling is not an error it just means you are using more than the capacity you purchased. Throttled is business as usual, and that is the first and most important But if you work with cloud databases, being If you are used to having your own database servers, you may
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |