medmunds
commented
1 month ago The logs you posted don't seem to show any significant delay. 08:37:16,955 minus 08:37:16,648 is 307 msec total from first to last log line:
DEBUG 2024-07-19 08:37:16,648 loaders 62693 140287951218368 Loading JSON file: … … DEBUG 2024-07-19 08:37:16,955 retryhandler 62693 140287951218368 No retry needed.
You might need to run some profiling to determine the actual culprit.
When you say "there's a significant delay," do you mean the call to Django's EmailMessage.send() or send_mail() or whatever blocks for 15 seconds? If the send call completes quickly, but then it takes 15 seconds for Amazon's email servers to actually get around to sending the message, that's not unusual. (And even if Amazon sends it instantly, but then it takes 15 seconds to arrive in the recipient's inbox, that's entirely normal. Email is rarely instantaneous.)
If your code is actually blocking for 15 seconds, then are you trying to send a large (1 MB+) email message or attachments and running in a CPU-limited environment? If so, there's a known issue that boto3 can be slow to sign large AWS API requests on constrained processors. (More details in boto/botocore#1561. The fix for that issue eliminated duplicated work in botocore, but couldn't do anything about the speed of Python's urlencode().)
If that's what you're running into, some options are:
- Use a slightly more powerful vCPU. A little bit can help a lot. (For reference, I regularly send email using boto3 SES in a Lambda Function limited to 128 MB and a 3 second timeout, without any trouble. Lambda CPU is proportional to memory, and 128 MB is the smallest Lambda allows.)
- As a workaround, you might try sending through SES's SMTP server with Django's built-in SMTP EmailBackend, instead of using django-anymail (or any other library built on boto3). Using SMTP avoids the need to build a signed AWS API request.
[If you go with the SMTP workaround, be aware that Django's SMTP EmailBackend assumes all SMTP servers properly handle Content-Transfer-Encoding: 8bit. Amazon SES doesn't, so if your message or text attachments have any non-ASCII characters this can result in Amazon SES sending mojibake.]
kjnez
Reporting an error? It's helpful to know:
ANYMAIL = { "AMAZON_SES_CLIENT_PARAMS": { "aws_access_key_id": AWS_ACCESS_KEY_ID, "aws_secret_access_key": AWS_SECRET_ACCESS_KEY, "region_name": AWS_S3_REGION_NAME, }, }