5 replies

Network latency Pro vs Free

I am based in Germany and am a little lost on something. Initially we used the free plan. DX and stuff was superb. We are now about to release our app.
While testing we experienced some sluggishness in regards to network response times on our end and shrugged it off as: Free tier now, we will go Pro anyway

Summa summarum: We upgraded and hoped to see some improvements. Our expectation was dev deployments are being allotted less resources and prod will most likely be fine. Nothing changed though. Even the simplest queries where we retrieve a doc directly by

id

id

.

I created a simple testbench which calls some functions of ours and timed the query/mutation/action calls and get the following result:

--- Starting Convex API Testbench ---

1. Checking if user '<redacted>' has 'read' access to project '<redacted>'...
'check_user_access' took 0.7853s
   => Access granted: True

2. Fetching user info for WorkOS ID '<redacted>'...
'get_user_by_workos_id' took 0.7779s
   => User Info: id=<redacted>, email=<redacted>

3. Fetching project details for project ID '<redacted>'...
'get_project_by_project_id' took 0.6383s
   => Project Details: {<redacted>}

4. Updating project '<redacted>'...
'update_project_by_id' took 0.7938s
   => Successfully updated project. New name: New Test Name - <redacted>

5. Fetching Stripe Customer ID for tenant '<redacted>'...
'get_customer_by_tenant' took 0.7705s
   => Customer ID: <redacted>

6. Fetching subscription ID for tenant '<redacted>'...
'get_subscription_by_tenant' took 0.7751s
   => Subscription ID not found (returned None).

7. Getting assets for project ID '<redacted>'...
'get_assets' took 0.7834s
   => Assets: <redacted>

--- Testbench Finished ---

--- Starting Convex API Testbench ---

1. Checking if user '<redacted>' has 'read' access to project '<redacted>'...
'check_user_access' took 0.7853s
   => Access granted: True

2. Fetching user info for WorkOS ID '<redacted>'...
'get_user_by_workos_id' took 0.7779s
   => User Info: id=<redacted>, email=<redacted>

3. Fetching project details for project ID '<redacted>'...
'get_project_by_project_id' took 0.6383s
   => Project Details: {<redacted>}

4. Updating project '<redacted>'...
'update_project_by_id' took 0.7938s
   => Successfully updated project. New name: New Test Name - <redacted>

5. Fetching Stripe Customer ID for tenant '<redacted>'...
'get_customer_by_tenant' took 0.7705s
   => Customer ID: <redacted>

6. Fetching subscription ID for tenant '<redacted>'...
'get_subscription_by_tenant' took 0.7751s
   => Subscription ID not found (returned None).

7. Getting assets for project ID '<redacted>'...
'get_assets' took 0.7834s
   => Assets: <redacted>

--- Testbench Finished ---

The associated execution times are shown in the provided screenshot.

This is in

prod

prod

with Python and consistent across multiple runs. I also did the same using the Rust

ConvexClient

ConvexClient

and saw better, but still unsatisfying latency metrics.

I will continue in my next message.

Network latency Pro vs Free

Similar Threads