Calcul de l'utilisation d'Akamai EdgeWorker

Events

En règle générale, une simple requête adressée à une URL protégée déclenche les événements suivants.

  1. 1x onClientRequest event
  2. 1x onClientRequest subrequest
  3. 1x onClientResponse event

Execution Statistics

Ces chiffres sont basés sur des moyennes arrondies calculées à partir d'un échantillon de 1 000 demandes d'utilisateurs finaux.

  1. Utilisation totale de la mémoire : 150 Ko
  2. Worker Initialization time + Worker Execution Time - 10ms

Strategies for Reducing EdgeWorker Hits

  1. Configure your property to only trigger the CrowdHandler EdgeWorker on domain paths that require protection. For example, if an average user journey hits 8 unique URLs, you may only need the CrowdHandler EdgeWorker to execute on a small subsection of these URLs, i.e., the entry point URL that customers are being directed to on your site. Consider consulting with the CrowdHandler support team (support@crowdhandler.com) to help optimize protected routes.
  2. Ensure that static asset file extensions such as css, js, and png do not trigger the CrowdHandler EdgeWorker. These file extensions will automatically be ignored during execution but by excluding them at the property level they will not trigger unnecessary EdgeWorker hits.