Flagship Transaction: Needs Improvement

[kpujjigit]

• [x] Verify all auto-instrumentation is working as it should
• [x] Understand and mitigate the gap in the span view (See Image Below)
• [x] Implement Custom Instrumentation (See Image Below) (get product guidance on "missing instrumentation")
• [x] Add client-side performance/profiling issue associated with a big span after the network call, like json encode on main thread

[armcknight]

Here's an example in the dashboard: https://demo.sentry.io/performance/mobile-ios:9cfb3fbe69534110bebcd64a7f36b730/?project=6249899&query=&referrer=performance-transaction-summary&statsPeriod=1h&transaction=EmpowerPlantViewController&unselectedSeries=p100%28%29&unselectedSeries=avg%28%29

[realkosty]

Proposal from Oct 3 iOS Jam:

• put a custom span around all of readCurrentDirectory()
• make readCurrentDirectory run faster - 3-4 seconds instead of 8 seconds (adjust Performance Issue thresholds in Settings if necessary)
• Make DB calls longer (that's why they don't show up in profiling right now)
  • Use existing "sleepy views" for that
• Consider making DB calls run on the same thread as the rest of the stuff - this allows us to tell a simpler demo story without concurrency.

[kpujjigit]

@armcknight how goes development on the above action items?

• Custom Instrumenting readCurrentDirectory

• Optimizing readCurrentDirectory

• Extending duration of DB Calls to appear in profiling

• Removing DB thread concurrency

[kpujjigit]

@kahest I think the last item we need to close this one out is to identify and instrument the missing instrumentation in our Flagship Transaction:

Example Transaction

[kahest]

@kpujjigit I didn't look into it closely, but I'm pretty sure that's the readCurrentDirectory - can you explain the purpose of this, and what the custom instrumentation should look like on the product?

[kpujjigit]

@kahest no further action needed here, this isn't a blocker so we'll leave it be. Thanks for chiming in.