Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
chore: new cached routes percent 10% (#897)
overall routing dashboard latency hasn't changed yet with 5%: ![Screenshot 2024-11-01 at 9.40.54 AM.png](https://graphite-user-uploaded-assets-prod.s3.amazonaws.com/BB54fKe6Y10GvrrdKXQN/9a8c7e6a-515d-47c5-ad25-92cf7ac38399.png) looking at [concurrentexecutions](https://us-east-2.console.aws.amazon.com/cloudwatch/home?region=us-east-2#metricsV2?graph=~(metrics~(~(~'AWS*2fLambda~'ProvisionedConcurrentExecutions~'FunctionName~'prod-us-east-2-RoutingAPI-R-RoutingLambda2C4DF0900-Bbcx5MI4vlM6)~(~'.~'ConcurrentExecutions~'.~'.)~(~'...~'prod-us-east-2-RoutingAPI-CachingRoutingLambdaFB79-E0BnTwVM2GKM))~view~'timeSeries~stacked~false~region~'us-east-2~start~'-PT24H~end~'P0D~stat~'Sum~period~300)&query=~'*7bAWS*2fLambda*2cFunctionName*7d*20concurrent), caching routing lambda def getting some traffic. But it's hard to tell if routing lambda concurrent executions went down yet because of traffic volume daily seasonality: ![Screenshot 2024-11-01 at 9.41.13 AM.png](https://graphite-user-uploaded-assets-prod.s3.amazonaws.com/BB54fKe6Y10GvrrdKXQN/669a5357-69af-4989-bdf0-81e39be72ae5.png) demed safe to ramp up to 10%
- Loading branch information