extremely high latency when using neon

our stack uses cf worker + hyperdrive + neon

we're are seeing some nasty latency, ranging from 1-4 seconds

+65ms       <-- GET /api/users/me
|  +65ms       starting workos auth
|  +336ms      after workos auth
|  +336ms      starting me
|  +336ms      before db user query
|  +2.51s      after db user query
|  +2.51s      --> GET /api/users/me 200 2s

+65ms       <-- GET /api/users/me
|  +65ms       starting workos auth
|  +336ms      after workos auth
|  +336ms      starting me
|  +336ms      before db user query
|  +2.51s      after db user query
|  +2.51s      --> GET /api/users/me 200 2s

+65ms       <-- GET /api/users/me
|  +65ms       starting workos auth
|  +336ms      after workos auth
|  +336ms      starting me
|  +336ms      before db user query
|  +2.51s      after db user query
|  +2.51s      --> GET /api/users/me 200 2s

+65ms       <-- GET /api/users/me
|  +65ms       starting workos auth
|  +336ms      after workos auth
|  +336ms      starting me
|  +336ms      before db user query
|  +2.51s      after db user query
|  +2.51s      --> GET /api/users/me 200 2s

we found that using hyperdrive, the walltime is ~400ms, and it worsens to 1s if using direct connection w/ or w/o pool

we checked neon's dashboard and latency seems fine < 20ms, and we tested it in <5min interval so unlikely the cold start.

can anyone please help take a look? this is very frustrating and we're seriously considering moving off neon

extremely high latency when using neon

Similar Threads

Similar Threads

Similar Threads