You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
So I am writing a SDK, and use aioboto3 as the base lib of my SDK. I have a a separate class to wrapping aioboto3 session, table and resources. And another class to perform the DB method, like put_item, delete_item, get_item... So what happens is that I tried to use the SDK I created to send multiple concurrent query to dynamodb. I got response time at the client side like:
I've added this change to my code, but I still observe this big diff. My test setup is like I have a container running in a EKS pod and in the same region with DynamoDB, let's say I send 10 requests to get the same item, then my response time looks like:
request_1: response time: 91 ms
request_2: response time: 200 ms
request_3: response time: 700 ms
request_4: response time: 1000 ms
request_5: response time: 1500 ms
request_6: response time: 100 ms
request_7: response time: 250 ms
request_8: response time: 800 ms
request_9: response time: 1600 ms
request_10: response time: 2000 ms
Another add-on question, if I use aiotboto3 resource whether it will be faster than aioboto3 client or not? if so how to construct resource connection in a correct way?
Description
So I am writing a SDK, and use aioboto3 as the base lib of my SDK. I have a a separate class to wrapping aioboto3 session, table and resources. And another class to perform the DB method, like put_item, delete_item, get_item... So what happens is that I tried to use the SDK I created to send multiple concurrent query to dynamodb. I got response time at the client side like:
What I Did
The aioboto3 session wraping code:
The text was updated successfully, but these errors were encountered: