throttle | A tool to use for rate limiting | Application Framework library

The correct way to use password-protected proxies with proxy-chain would be this:

Your setupSnapshot() function is being called before the values have been accepted into followers. I haven't used a NSDiffableDataSourceSnapshot yet, but you likely need to do something like this instead:

You need to await the page.goto("...")

Since API Gateway is triggered first & its before your main lambda you cannot control the Gateway from the lambda itself.

But, API Gateway has a custom authoriser (Lambda authorizer) which is triggered first if enabled and once executed the request is passed to main lambda.

You can write the throttling code in lambda and attach that lambda as custom authoriser to API Gateway. This lambda can now approve or reject requests based on your throttling logic.

https://docs.aws.amazon.com/apigateway/latest/developerguide/apigateway-use-lambda-authorizer.html

However, a more straight forward solution will be using AWS WAF using which you can directly configure IP based throttling rule.

https://support.stackpath.com/hc/en-us/articles/360001380266-Create-a-Rate-Limit-Rule-with-the-WAF

Since there's no way to guarantee the order of execution, it's hard to find a to write this particular function. But I can think of a few work-around for the problem you have:

1. It sounds like you are only rapidly updating right after it's created? In that case maybe what can work is having your create write to a draft collection and have your update copy the updated data into the searchable collection.
2. Rather than updating, add new documents with timestamp and filter the result at query-time.
3. If your client can tolerate stale data, you can have a scheduled function that syncs all documents with Algolia.

Well, for starters, you don't need to convert your downloaded string to an ASCII encoded TBytes. TJSONObject.ParseJSONValue() has an overload that takes a string as input.

Second, LJsonObj.Get('ATTITUDE').JsonValue will return a TJSONObject, which you are incorrectly type-casting to a TJSONPair. But that doesn't matter, since you are then ignoring that TJSONPair and instead incorrectly type-casting the input parameter sVALUE from a string to a TJSONPair and then trying to access its children. That is why you are getting the Access Violation.

But even if you were able to find the TJSONPair for the roll value, you are returning the string value of its JsonString (name) property, not the string value of its JsonValue (value) property.

Try this instead:

Your hook's signature is not the same as when you call it.

Perhaps you should do something along these lines:

The error occurs because the only way to throttle IO using cgroups version 1 is to use a device that is physical. The major and minor version numbers I used above are for a partition. You need to pick the major and minor numbers for the physical device that HOLDS the partition.

Answer can be found in this post MVC memory issue, memory not getting cleared after controller call is finished (Example project included)

Copied answer

The github version is a fixed version for this issue, so you can go explorer what i did in the changeset

Notes:

1. After generating a large file, you might need to download smaller sized files before C# releases the memory
2. Adding forced garbage collection helped alot
3. Adding a few using statements also helped alot

Smaller existing issues

1. If your object cant fit in the RAM and it start filling the pagefile it will not reduce the pagefile after use(Restarting your pc will help a little on it but wont clear the pagefile entirely)
2. I couldnt get it below 400MB of ram usage no matter what i tried, but it didnt matter if i had 5GB or 1GB in the RAM it would still get reduced down to ~400 MB