Data API is slow

MongoDB Atlas App Services & Realm Atlas Data API
1

I am trying to call data-api from postman, it’s taking nearly 3 seconds to give response. Is it the normal case? Because querying through connection URL is a lot more faster than this. Will data Api give the same performance as we get from connection URL or it’s slower than the other method.

Following are the details of my cluster :

Screenshot 2022-05-05 160300
Screenshot 2022-05-05 1603001618×458 42.9 KB

WhatsApp Image 2022-05-05 at 4.12.29 PM
WhatsApp Image 2022-05-05 at 4.12.29 PM1280×339 20.6 KB

2 Likes
2

There is a lot more going on with Data API compared to a driver connection.

  1. The folllowing only occurs with the DataAPI - You start with a connection that is not established between postman and the web server that
    handle your request.
  2. This web server, as far as I know, is shared and might not have a connection established between itself and your atlas cluster.
  3. This web server has to interpret your request and create one for the cluster using the driver connection. From here the performance should match what you see from your driver as it is the same.
  4. The database server handle the request and send the response to the driver.
  5. Once the web server receive the answer it has to repackage it into an http response. The rest only occurs with Data API.
  6. You finally can read and process the response.

So a lot more is going on.

Data API is very convenient because it is a layer of abstraction where you do not have to manage an application server. But it comes at a performance cost. You have to be aware of that.

3 Likes
3

Hi @VIKASH_KUMAR_SHUKLA welcome to the community!

I would also like to point out that the Data API is still very much in Preview/Beta at this moment, so things might change for the better in the future.

Best regards
Kevin

3 Likes
4

Hi Vikash - I’ll also jump in and add that we have some improvements planned that will make this much faster, including some optimizations internally and the ability to externally choose a better deployment model fit for your region and cloud provider.
Currently I can see you’ve deployed your cluster on GCP which may cause some latency since the API is default hosted on AWS which may lead to some cross-cloud latency.

2 Likes
5

Thank you Sumedha, I got your point. Now the problem is that we have deployed our Node Js (Back End) + React Js (Front End) on Google Cloud Platform. Also, our mongoDB cluster is deployed on GCP to reduce any latency. My questions are :

  1. Will the latency increase if we migrate our mongoDB cluster to AWS.
  2. Is it better to deploy mongodb as a service on Google Cloud Platform (from google cloud marketplace) rather than using a separate instance on cloud.mongodb.com. Will it improve our api performance if we deploy it there itself as service?
8

Hi, is the data api still in beta.

Was hoping to be able to use this in production, we too are seeing 4-5 seconds delay (calling from a cloudflare worker)

We may shift some of our data storage to cloudflare d1 or kv stores… really looking for data to be stored at the edge.

1 Like
9

Any updates tot the Data API, seems like there isnt a roadmap listed as to how this service can improve. Queries such as findOneAndUpdate are not supported not to mention the lengthly connection times.