Loading feed…
AWS Database Blog0 Hot0 comments13 min read
Characterizing SQL*Net latency in your application for Oracle Database@AWS migrations
A three-phase methodology called CRET (Client Request Elapsed Time) is presented to help teams assess whether their Oracle workloads are sensitive to SQLNet latency before migrating to Oracle Database@AWS (ODB@AWS). Phase 1 uses AWR reports to identify SQL statements with sub-millisecond database processing time and high execution frequency. Phase 2 checks SQL Execution Session Density to confirm executions are concentrated in few sessions. Phase 3 uses SQL Trace and a set of AWK one-liners to quantify projected runtime impact from added SQLNet round-trip latency. Worked examples contrast a tight-loop trace (highly sensitive to added latency) against a client-delay trace (tolerant), and an interpretation table classifies workloads as tolerant, borderline, or sensitive based on projected percentage impact. Connectivity recommendations include co-locating application tiers with ODB Peering and enabling ODB@AWS high-performance networking for sub-millisecond round-trip latency.
Source: https://aws.amazon.com/blogs/database/characterizing-sqlnet-latency-in-your-application-for-oracle-databaseaws-migrations. 8 Sync News only summarizes and links out; content copyright belongs to the authors and original sources.
