eschweinsberg-api-latency | Stripe Developers | Page 1

tidal escarp Dec 8, 2021, 2:20 PM

#

Hi there 👋 7 seconds sounds a bit high. Some operations, like creating subscriptions, do take a little while due to the number of underlying operations. Do you have a request ID that you could share where you saw this timing?

sonic thorn Dec 8, 2021, 2:22 PM

#

Whoops, actually the request was updating the metadata on an invoice, not finalizing it. Here's the request ID: req_91QPrhaHCaZD9b

tidal escarp Dec 8, 2021, 2:27 PM

#

Thanks for that! Our logs are showing that request executed end-to-end in under 1.5 seconds though.

sonic thorn Dec 8, 2021, 2:31 PM

#

Hmm okay, that's odd. My request tracing and the stripe-go library are reporting 7 seconds. Maybe something is wrong with my instrumentation.

cyan elbow Dec 8, 2021, 2:33 PM

#

it's also possible that there's some networking wonkiness happening between your server & stripe

#

are you seeing this persistently, or sporadically?

sonic thorn Dec 8, 2021, 2:41 PM

#

I'm seeing it persistently, although not quite as bad as the original request I reported. For example, req_2TrLKhXvAcN0qY is showing 4.6 seconds on my end

#

Would it matter that this is in the test environment?

tidal escarp Dec 8, 2021, 2:46 PM

#

Hm, that one is showing that it did take about 4.5 seconds to complete.

sonic thorn Dec 8, 2021, 2:50 PM

#

Oh I may have given you the wrong ID before, is this one showing around 7? req_K9Zn688gZz1myF

cyan elbow Dec 8, 2021, 2:54 PM

#

req_2TrLKhXvAcN0qY looks to be slow b/c of lock contention - you have (at least) two API requests in flight. the one you linked is trying to update the invoice, and another is trying to update the customer. both need an exclusive lock on the customer to run, so one queues behind the other

sonic thorn Dec 8, 2021, 2:56 PM

#

ahh okay. that makes sense

cyan elbow Dec 8, 2021, 2:56 PM

#

req_K9Zn688gZz1myF seems to have similar lock problems

#eschweinsberg-api-latency