By default, lambda functions are deployed in the us-east-1 AWS Lambda region. Do you happen to know where your fauna DB is hosted? Perhaps your database instance in not very near. Let me know if that makes sense.
Hi,
Thx for the reply. I think fauna has to be located in THE US somewhere. Otherwise 300kb wouldn’t take that long. Im located in Estonia. I think any EU region would be OK for me (us-east-1 eg.). Gonna try and figure out where and how can i move my fauna instance closer. Or maybe use another service provider. (not sure which)
Added 3 time measurements… looks as if the time spent after recieving entities is also quite long
Improved version of the initial image with output below
If you could provide the url of your function, I can check the logs on our end. Those logs typically have a timing attribute so that should give us some idea if the extra time is in your code or in our system.