summaryrefslogtreecommitdiff
path: root/requests_cache/backends
diff options
context:
space:
mode:
authorJordan Cook <jordan.cook@pioneer.com>2021-08-20 23:17:06 -0500
committerJordan Cook <jordan.cook@pioneer.com>2021-08-20 23:17:06 -0500
commite6fff586cd94685e7a8354170e070cb692ad4430 (patch)
treebae47940232ba51b07c8a3cab5298cc18dcd384a /requests_cache/backends
parent9c89fe2a5f696e2ea786fb368529e3cb421c0b57 (diff)
downloadrequests-cache-e6fff586cd94685e7a8354170e070cb692ad4430.tar.gz
Add CLI arg to benchmark script to select a backend
Diffstat (limited to 'requests_cache/backends')
-rw-r--r--requests_cache/backends/dynamodb.py4
-rw-r--r--requests_cache/backends/sqlite.py2
2 files changed, 5 insertions, 1 deletions
diff --git a/requests_cache/backends/dynamodb.py b/requests_cache/backends/dynamodb.py
index b97952a..d30d55f 100644
--- a/requests_cache/backends/dynamodb.py
+++ b/requests_cache/backends/dynamodb.py
@@ -7,6 +7,10 @@ Services <https://aws.amazon.com>`_. In terms of features and use cases, it is r
MongoDB and other NoSQL databases. It is an especially good fit for serverless applications running
on `AWS Lambda <https://aws.amazon.com/lambda>`_.
+.. warning::
+ DynamoDB binary item sizes are limited to 400KB. If you need to cache larger responses, consider
+ using a different backend.
+
Connection Options
^^^^^^^^^^^^^^^^^^
The DynamoDB backend accepts any keyword arguments for :py:meth:`boto3.session.Session.resource`.
diff --git a/requests_cache/backends/sqlite.py b/requests_cache/backends/sqlite.py
index 4429bc9..a66e228 100644
--- a/requests_cache/backends/sqlite.py
+++ b/requests_cache/backends/sqlite.py
@@ -92,7 +92,7 @@ When working with average-sized HTTP responses (< 1MB) and using a modern SSD fo
can expect speeds of around:
* Write: 2-8ms
-* Read: 0.3-0.6ms
+* Read: 0.2-0.6ms
Of course, this will vary based on hardware specs, response size, and other factors.