btoueg

resource "datadog_synthetics" "foo" {
  # Every attributes required to create a new Datadog synthetics test
  name               = "Name for synthetics foo"
  type               = "api"
  message            = "Synthetics test failed. Notify: @slack-channel"
  options {
    tick_every = 60
  }
  config {
    request {

btoueg

<?php

// Show all information, defaults to INFO_ALL
phpinfo();

?>

btoueg

# -*- encoding: utf-8 -*-

import base64
import logging

from cryptography.exceptions import UnsupportedAlgorithm
from cryptography.hazmat.backends import default_backend
from cryptography.hazmat.primitives import hashes
from cryptography.hazmat.primitives import serialization
from cryptography.hazmat.primitives.asymmetric import padding

btoueg

# -*- encoding: utf-8 -*-

import os
import base64
from cryptography.hazmat.primitives.ciphers import Cipher, algorithms, modes
from cryptography.hazmat.backends import default_backend

backend = default_backend()
secret_key = base64.b64decode(
    # generated randomly once, kept secret

btoueg

I'm trying to achieve fine-grained throttling with aiohttp.

By fine-grained, I mean that controlling how many requests are simultaneously executed is not enough, I want to rate-limit the number of requests to match 100 requests per 10 seconds interval.

The interesting part resides in throttled_coroutine which acquires/releases a lock at a speed which is exactly the rate-limit I want to enforce by either:

• waiting a delay once requests performing very quickly are completed
• releasing lock before completion of requests performing poorly

At the end of a batch of requests, last coroutines tend to wait for no reason. This behaviour amplifies when timeout increases.

btoueg

# -*- coding: utf-8 -*-

import json
import requests
from requests_oauthlib import OAuth1
from oauthlib.oauth1 import SIGNATURE_PLAINTEXT, SIGNATURE_TYPE_BODY

consumer_token = '***'
consumer_secret = '***'
user_token = '***'