mirror of
https://github.com/pacnpal/django-anymail.git
synced 2025-12-20 11:51:05 -05:00
61660cd5ff
Switch from the (now unmaintained) python-sparkpost client library to a requests-based backend that calls SparkPost's Transmissions API directly. Also adds support for text/x-amp-html alternative parts (which are supported by the SparkPost API, but weren't by the client library). Closes #203
20 lines
940 B
ReStructuredText
20 lines
940 B
ReStructuredText
.. _performance:
|
|
|
|
Batch send performance
|
|
======================
|
|
|
|
If you are sending batches of hundreds of emails at a time, you can improve
|
|
performance slightly by reusing a single HTTP connection to your ESP's
|
|
API, rather than creating (and tearing down) a new connection for each message.
|
|
|
|
Most Anymail EmailBackends automatically reuse their HTTP connections when
|
|
used with Django's batch-sending functions :func:`~django.core.mail.send_mass_mail` or
|
|
:meth:`connection.send_messages`. See :ref:`django:topics-sending-multiple-emails`
|
|
in the Django docs for more info and an example.
|
|
|
|
If you need even more performance, you may want to consider your ESP's batch-sending
|
|
features. When supported by your ESP, Anymail can send multiple messages with a single
|
|
API call. See :ref:`batch-send` for details, and be sure to check the
|
|
:ref:`ESP-specific info <supported-esps>` because batch sending capabilities vary
|
|
significantly between ESPs.
|