Performance Profiling

Performance profiling is the systematic analysis of query execution to identify bottlenecks, optimize resource usage, and improve response times. In Geode, profiling capabilities provide detailed insights into how GQL queries execute, enabling data-driven optimization decisions for graph database workloads. <h3 id="understanding-performance-profiling" class="position-relative d-flex align-items-center group"> Understanding Performance Profiling <button type="button" class="h-share btn btn-link p-0 text-decoration-none link-secondary opacity-50 hover-opacity-100 transition-all ms-1" data-share-target="understanding-performance-profiling" aria-haspopup="dialog" aria-label="Share link: Understanding Performance Profiling"> Share link </button> </h3><div id="headingShareModal" class="heading-share-modal" role="dialog" aria-modal="true" aria-labelledby="headingShareTitle" hidden> <div class="hsm-dialog" role="document"> <div class="hsm-header"> <h2 id="headingShareTitle" class="h6 mb-0 fw-bold">Share this section</h2> <button type="button" class="hsm-close" aria-label="Close"> </button> </div> <div class="hsm-body"> <label for="headingShareInput" class="form-label small text-muted mb-1 text-uppercase fw-bold" style="font-size: 0.7rem; letter-spacing: 0.5px;">Permalink</label> <div class="input-group mb-4 hsm-url-group"> <input id="headingShareInput" type="text" class="form-control font-monospace" readonly aria-readonly="true" style="font-size: 0.85rem;" /> <button class="btn btn-primary hsm-copy" type="button" aria-label="Copy" title="Copy"> </button> </div> <div class="small fw-bold mb-2 text-muted text-uppercase" style="font-size: 0.7rem; letter-spacing: 0.5px;">Share via</div> <div class="hsm-share-grid"> <a id="share-twitter" class="btn btn-outline-secondary w-100" target="_blank" rel="noopener noreferrer"> Twitter </a> <a id="share-linkedin" class="btn btn-outline-secondary w-100" target="_blank" rel="noopener noreferrer"> LinkedIn </a> <a id="share-facebook" class="btn btn-outline-secondary w-100" target="_blank" rel="noopener noreferrer"> Facebook </a> </div> </div> </div> </div> <style> .heading-share-modal { position: fixed; inset: 0; display: flex; justify-content: center; align-items: center; background: rgba(0, 0, 0, 0.6); z-index: 1050; padding: 1rem; backdrop-filter: blur(4px); -webkit-backdrop-filter: blur(4px); } .heading-share-modal[hidden] { display: none !important; } .hsm-dialog { max-width: 420px; width: 100%; background: var(--bs-body-bg, #fff); color: var(--bs-body-color, #212529); border: 1px solid var(--bs-border-color, rgba(0,0,0,0.1)); border-radius: 1rem; box-shadow: 0 25px 50px -12px rgba(0, 0, 0, 0.25); overflow: hidden; animation: hsm-fade-in 0.2s ease-out; } @keyframes hsm-fade-in { from { opacity: 0; transform: scale(0.95); } to { opacity: 1; transform: scale(1); } } [data-bs-theme="dark"] .hsm-dialog { background: #1e293b; border-color: rgba(255,255,255,0.1); color: #f8f9fa; } .hsm-header { display: flex; justify-content: space-between; align-items: center; padding: 1rem 1.5rem; border-bottom: 1px solid var(--bs-border-color, rgba(0,0,0,0.1)); background: rgba(0,0,0,0.02); } [data-bs-theme="dark"] .hsm-header { background: rgba(255,255,255,0.02); border-color: rgba(255,255,255,0.1); } .hsm-close { background: transparent; border: none; color: inherit; opacity: 0.5; padding: 0.25rem 0.5rem; border-radius: 0.25rem; font-size: 1.2rem; line-height: 1; transition: opacity 0.2s; } .hsm-close:hover { opacity: 1; } .hsm-body { padding: 1.5rem; } .hsm-url-group { display: flex !important; align-items: stretch; } .hsm-url-group .form-control { flex: 1; min-width: 0; margin: 0; background: var(--bs-secondary-bg, #f8f9fa); border-color: var(--bs-border-color, #dee2e6); border-top-right-radius: 0; border-bottom-right-radius: 0; height: 42px; } .hsm-url-group .btn { flex: 0 0 auto; margin: 0; margin-left: -1px; border-top-left-radius: 0; border-bottom-left-radius: 0; height: 42px; display: flex; align-items: center; justify-content: center; padding: 0 1.25rem; z-index: 2; } [data-bs-theme="dark"] .hsm-url-group .form-control { background: #0f172a; border-color: #334155; color: #e2e8f0; } .hsm-share-grid { display: flex; flex-direction: column; gap: 0.5rem; } .hsm-share-grid .btn { display: flex; align-items: center; justify-content: center; font-size: 0.9rem; padding: 0.6rem; border-color: var(--bs-border-color); width: 100%; } [data-bs-theme="dark"] .hsm-share-grid .btn { color: #e2e8f0; border-color: #475569; } [data-bs-theme="dark"] .hsm-share-grid .btn:hover { background: #334155; border-color: #cbd5e1; } </style> <script> (function(){ const modal = document.getElementById('headingShareModal'); if(!modal) return; const input = modal.querySelector('#headingShareInput'); const copyBtn = modal.querySelector('.hsm-copy'); const twitter = modal.querySelector('#share-twitter'); const linkedin = modal.querySelector('#share-linkedin'); const facebook = modal.querySelector('#share-facebook'); const closeBtn = modal.querySelector('.hsm-close'); let lastFocus=null; let trapBound=false; function buildUrl(id){ return window.location.origin + window.location.pathname + '#' + id; } function isOpen(){ return !modal.hasAttribute('hidden'); } function hydrate(id){ const url=buildUrl(id); input.value=url; const enc=encodeURIComponent(url); const text=encodeURIComponent(document.title); if(twitter) twitter.href=`https://twitter.com/intent/tweet?url=${enc}&text=${text}`; if(linkedin) linkedin.href=`https://www.linkedin.com/sharing/share-offsite/?url=${enc}`; if(facebook) facebook.href=`https://www.facebook.com/sharer/sharer.php?u=${enc}`; } function openModal(id){ lastFocus=document.activeElement; hydrate(id); if(!isOpen()){ modal.removeAttribute('hidden'); } requestAnimationFrame(()=>{ input.focus(); }); trapFocus(); } function closeModal(){ if(!isOpen()) return; modal.setAttribute('hidden',''); if(lastFocus && typeof lastFocus.focus==='function') lastFocus.focus(); } function copyCurrent(){ try{ navigator.clipboard.writeText(input.value).then(()=>feedback(true),()=>fallback()); } catch(e){ fallback(); } } function fallback(){ input.select(); try{ document.execCommand('copy'); feedback(true);}catch(e){ feedback(false);} } function feedback(ok){ if(!copyBtn) return; const icon=copyBtn.querySelector('i'); if(!icon) return; const prev=copyBtn.getAttribute('data-prev')||icon.className; if(!copyBtn.getAttribute('data-prev')) copyBtn.setAttribute('data-prev',prev); icon.className= ok ? 'fa-duotone fa-clipboard-check':'fa-duotone fa-circle-exclamation'; setTimeout(()=>{ icon.className=prev; },1800); } function handleShareClick(e){ e.preventDefault(); const btn=e.currentTarget; const id=btn.getAttribute('data-share-target'); if(id) openModal(id); } function bindShareButtons(){ document.querySelectorAll('.h-share').forEach(btn=>{ if(!btn.dataset.hShareBound){ btn.addEventListener('click', handleShareClick); btn.dataset.hShareBound='1'; } }); } bindShareButtons(); if(document.readyState==='loading'){ document.addEventListener('DOMContentLoaded', bindShareButtons); } else { requestAnimationFrame(bindShareButtons); } document.addEventListener('click', function(e){ const shareBtn=e.target.closest && e.target.closest('.h-share'); if(shareBtn && !shareBtn.dataset.hShareBound){ handleShareClick.call(shareBtn, e); } }, true); document.addEventListener('click', e=>{ if(e.target===modal) closeModal(); if(e.target.closest && e.target.closest('.hsm-close')){ e.preventDefault(); closeModal(); } if(copyBtn && (e.target===copyBtn || (e.target.closest && e.target.closest('.hsm-copy')))) { e.preventDefault(); copyCurrent(); } }); document.addEventListener('keydown', e=>{ if(e.key==='Escape' && isOpen()) closeModal(); }); function trapFocus(){ if(trapBound) return; trapBound=true; modal.addEventListener('keydown', f=>{ if(f.key==='Tab' && isOpen()){ const focusable=[...modal.querySelectorAll('a[href],button,input,textarea,select,[tabindex]:not([tabindex="-1"])')].filter(el=>!el.hasAttribute('disabled')); if(!focusable.length) return; const first=focusable[0]; const last=focusable[focusable.length-1]; if(f.shiftKey && document.activeElement===first){ f.preventDefault(); last.focus(); } else if(!f.shiftKey && document.activeElement===last){ f.preventDefault(); first.focus(); } } }); } if(closeBtn) closeBtn.addEventListener('click', e=>{ e.preventDefault(); closeModal(); }); })(); </script>Performance profiling reveals the internal execution characteristics of database queries, exposing where time is spent and resources are consumed. For graph databases like Geode, profiling becomes particularly important due to the complex traversal patterns and relationship-heavy operations that can exhibit non-linear performance characteristics. <h4 id="why-profile-graph-queries" class="position-relative d-flex align-items-center group"> Why Profile Graph Queries <button type="button" class="h-share btn btn-link p-0 text-decoration-none link-secondary opacity-50 hover-opacity-100 transition-all ms-1" data-share-target="why-profile-graph-queries" aria-haspopup="dialog" aria-label="Share link: Why Profile Graph Queries"> Share link </button> </h4>Graph queries differ fundamentally from relational queries. A graph traversal can touch a few nodes or millions, depending on data density and relationship patterns. Without profiling, developers operate blind to execution efficiency, potentially deploying queries that perform well on test data but degrade dramatically in production. Profiling provides concrete metrics on execution time, rows processed, index utilization, and memory consumption. This empirical evidence guides optimization efforts toward the operations that actually impact performance, rather than premature optimization based on assumptions. <h4 id="profiling-vs-explaining" class="position-relative d-flex align-items-center group"> Profiling vs. Explaining <button type="button" class="h-share btn btn-link p-0 text-decoration-none link-secondary opacity-50 hover-opacity-100 transition-all ms-1" data-share-target="profiling-vs-explaining" aria-haspopup="dialog" aria-label="Share link: Profiling vs. Explaining"> Share link </button> </h4>Geode provides two complementary analysis tools: EXPLAIN shows the query execution plan without running the query, while PROFILE executes the query and provides actual runtime metrics. EXPLAIN helps understand what the optimizer intends to do, while PROFILE reveals what actually happened during execution. <h3 id="the-profile-command" class="position-relative d-flex align-items-center group"> The PROFILE Command <button type="button" class="h-share btn btn-link p-0 text-decoration-none link-secondary opacity-50 hover-opacity-100 transition-all ms-1" data-share-target="the-profile-command" aria-haspopup="dialog" aria-label="Share link: The PROFILE Command"> Share link </button> </h3>Geode’s PROFILE command executes a query while collecting detailed performance metrics. <h4 id="basic-profiling" class="position-relative d-flex align-items-center group"> Basic Profiling <button type="button" class="h-share btn btn-link p-0 text-decoration-none link-secondary opacity-50 hover-opacity-100 transition-all ms-1" data-share-target="basic-profiling" aria-haspopup="dialog" aria-label="Share link: Basic Profiling"> Share link </button> </h4>The simplest profiling workflow prefixes any GQL query with the PROFILE keyword: <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-gql" data-lang="gql">PROFILE MATCH (n:Person) WHERE n.age > 30 RETURN n.name, n.age; </code></pre></div>This executes the query normally but returns additional metadata about execution characteristics, including: <ul> <li>Total execution time</li> <li>Rows examined vs. rows returned</li> <li>Index usage statistics</li> <li>Memory allocation patterns</li> <li>Join and traversal metrics</li> </ul> <h4 id="interpreting-profile-output" class="position-relative d-flex align-items-center group"> Interpreting Profile Output <button type="button" class="h-share btn btn-link p-0 text-decoration-none link-secondary opacity-50 hover-opacity-100 transition-all ms-1" data-share-target="interpreting-profile-output" aria-haspopup="dialog" aria-label="Share link: Interpreting Profile Output"> Share link </button> </h4>Profile output includes multiple sections, each providing specific insights into query execution. The execution summary shows overall timing: <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-fallback" data-lang="fallback">Execution Time: 45.2ms Rows Examined: 15,420 Rows Returned: 3,847 Index Scans: 1 (Person.age) Full Scans: 0 </code></pre></div>This immediately reveals efficiency: the query scanned 15,420 rows to return 3,847, indicating reasonable selectivity. The index scan on Person.age avoided a full table scan. <h4 id="detailed-execution-steps" class="position-relative d-flex align-items-center group"> Detailed Execution Steps <button type="button" class="h-share btn btn-link p-0 text-decoration-none link-secondary opacity-50 hover-opacity-100 transition-all ms-1" data-share-target="detailed-execution-steps" aria-haspopup="dialog" aria-label="Share link: Detailed Execution Steps"> Share link </button> </h4>More detailed profiling breaks down execution into individual operations: <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-fallback" data-lang="fallback">1. Index Scan (Person.age > 30) Time: 12.3ms Rows: 15,420 2. Property Access (n.name, n.age) Time: 18.7ms Rows: 15,420 3. Result Materialization Time: 14.2ms Rows: 3,847 </code></pre></div>This granular breakdown identifies the property access phase as the primary time consumer, suggesting potential optimization through projection reduction or property indexing. <h3 id="profiling-graph-traversals" class="position-relative d-flex align-items-center group"> Profiling Graph Traversals <button type="button" class="h-share btn btn-link p-0 text-decoration-none link-secondary opacity-50 hover-opacity-100 transition-all ms-1" data-share-target="profiling-graph-traversals" aria-haspopup="dialog" aria-label="Share link: Profiling Graph Traversals"> Share link </button> </h3>Graph traversals present unique profiling challenges due to their recursive and relationship-oriented nature. <h4 id="simple-traversal-profiling" class="position-relative d-flex align-items-center group"> Simple Traversal Profiling <button type="button" class="h-share btn btn-link p-0 text-decoration-none link-secondary opacity-50 hover-opacity-100 transition-all ms-1" data-share-target="simple-traversal-profiling" aria-haspopup="dialog" aria-label="Share link: Simple Traversal Profiling"> Share link </button> </h4>A basic friend-of-friend query demonstrates traversal profiling: <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-gql" data-lang="gql">PROFILE MATCH (p:Person {name: 'Alice'})-[:KNOWS]->(friend)-[:KNOWS]->(fof) RETURN DISTINCT fof.name; </code></pre></div>Profile output reveals traversal efficiency: <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-fallback" data-lang="fallback">Execution Time: 156.8ms Traversal Depth: 2 Starting Nodes: 1 (index lookup) Intermediate Nodes: 47 (first hop) Final Nodes: 892 (second hop) Distinct Results: 623 </code></pre></div>The expanding traversal from 1 to 47 to 892 nodes shows typical graph “fan-out” behavior. The DISTINCT operation reduced 892 nodes to 623 unique results, indicating some overlap in friend networks. <h4 id="variable-length-path-profiling" class="position-relative d-flex align-items-center group"> Variable-Length Path Profiling <button type="button" class="h-share btn btn-link p-0 text-decoration-none link-secondary opacity-50 hover-opacity-100 transition-all ms-1" data-share-target="variable-length-path-profiling" aria-haspopup="dialog" aria-label="Share link: Variable-Length Path Profiling"> Share link </button> </h4>Variable-length paths can have unpredictable performance: <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-gql" data-lang="gql">PROFILE MATCH (p:Person {name: 'Alice'})-[:KNOWS*1..3]->(connected) RETURN connected.name, length(path) AS distance; </code></pre></div>Profiling variable-length paths reveals how many paths were explored: <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-fallback" data-lang="fallback">Execution Time: 2,341ms Paths Explored: 45,672 Paths Matched: 1,124 Average Path Length: 1.8 Max Path Length: 3 Traversal Strategy: Breadth-First </code></pre></div>The large difference between explored (45,672) and matched (1,124) paths indicates significant pruning. If this ratio is too high, constraining the search with additional filters can improve performance. <h4 id="traversal-strategy-analysis" class="position-relative d-flex align-items-center group"> Traversal Strategy Analysis <button type="button" class="h-share btn btn-link p-0 text-decoration-none link-secondary opacity-50 hover-opacity-100 transition-all ms-1" data-share-target="traversal-strategy-analysis" aria-haspopup="dialog" aria-label="Share link: Traversal Strategy Analysis"> Share link </button> </h4>Geode’s optimizer chooses traversal strategies based on query patterns. Profiling reveals which strategy was selected: <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-fallback" data-lang="fallback">Traversal Strategy: Depth-First Search Reasoning: Low branching factor detected Nodes Visited: 234 Backtracking Events: 12 </code></pre></div>Understanding the chosen strategy helps evaluate whether the optimizer made optimal decisions for the actual data distribution. <h3 id="profiling-aggregations" class="position-relative d-flex align-items-center group"> Profiling Aggregations <button type="button" class="h-share btn btn-link p-0 text-decoration-none link-secondary opacity-50 hover-opacity-100 transition-all ms-1" data-share-target="profiling-aggregations" aria-haspopup="dialog" aria-label="Share link: Profiling Aggregations"> Share link </button> </h3>Aggregation queries require profiling to understand grouping and computation costs. <h4 id="group-by-performance" class="position-relative d-flex align-items-center group"> Group By Performance <button type="button" class="h-share btn btn-link p-0 text-decoration-none link-secondary opacity-50 hover-opacity-100 transition-all ms-1" data-share-target="group-by-performance" aria-haspopup="dialog" aria-label="Share link: Group By Performance"> Share link </button> </h4>Profiling a grouped aggregation: <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-gql" data-lang="gql">PROFILE MATCH (p:Person)-[:WORKS_AT]->(c:Company) RETURN c.name, count(p) AS employees, avg(p.salary) AS avg_salary ORDER BY employees DESC; </code></pre></div>Profile output breaks down aggregation costs: <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-fallback" data-lang="fallback">Execution Time: 234.5ms Traversal Time: 89.2ms (Person -> Company) Grouping Time: 78.3ms (12 groups) Aggregation Time: 45.6ms (count, avg) Sorting Time: 21.4ms Rows Processed: 8,456 Groups Created: 12 </code></pre></div>The grouping operation consumed the most time after traversal. With only 12 groups from 8,456 rows, the grouping is highly selective, which is efficient. <h4 id="complex-aggregation-analysis" class="position-relative d-flex align-items-center group"> Complex Aggregation Analysis <button type="button" class="h-share btn btn-link p-0 text-decoration-none link-secondary opacity-50 hover-opacity-100 transition-all ms-1" data-share-target="complex-aggregation-analysis" aria-haspopup="dialog" aria-label="Share link: Complex Aggregation Analysis"> Share link </button> </h4>Nested aggregations or aggregations over traversals can be expensive: <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-gql" data-lang="gql">PROFILE MATCH (p:Person)-[:KNOWS]->(friend)-[:LIKES]->(product:Product) RETURN p.name, count(DISTINCT friend) AS friend_count, collect(DISTINCT product.name) AS liked_products; </code></pre></div>Profile output reveals collection costs: <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-fallback" data-lang="fallback">Execution Time: 1,567ms Distinct Operations: 2 (friend, product) Collections Built: 847 (one per person) Collection Avg Size: 12.3 products Memory Allocated: 23.4MB </code></pre></div>The memory allocation metric becomes critical for large result sets, indicating potential memory pressure. <h3 id="index-usage-profiling" class="position-relative d-flex align-items-center group"> Index Usage Profiling <button type="button" class="h-share btn btn-link p-0 text-decoration-none link-secondary opacity-50 hover-opacity-100 transition-all ms-1" data-share-target="index-usage-profiling" aria-haspopup="dialog" aria-label="Share link: Index Usage Profiling"> Share link </button> </h3>Indexes dramatically affect performance, making index usage profiling essential. <h4 id="index-scan-detection" class="position-relative d-flex align-items-center group"> Index Scan Detection <button type="button" class="h-share btn btn-link p-0 text-decoration-none link-secondary opacity-50 hover-opacity-100 transition-all ms-1" data-share-target="index-scan-detection" aria-haspopup="dialog" aria-label="Share link: Index Scan Detection"> Share link </button> </h4>Profiling reveals whether indexes were used: <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-gql" data-lang="gql">PROFILE MATCH (p:Person) WHERE p.email = 'alice@example.com' RETURN p; </code></pre></div>Ideal profile output shows index usage: <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-fallback" data-lang="fallback">Execution Time: 2.3ms Index Used: Person.email (unique) Index Scan Time: 1.8ms Rows Examined: 1 Rows Returned: 1 </code></pre></div>Without an index, the profile would show: <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-fallback" data-lang="fallback">Execution Time: 145.7ms Full Table Scan: Person Rows Examined: 15,420 Rows Returned: 1 </code></pre></div>The dramatic difference (2.3ms vs 145.7ms) demonstrates index value. <h4 id="composite-index-analysis" class="position-relative d-flex align-items-center group"> Composite Index Analysis <button type="button" class="h-share btn btn-link p-0 text-decoration-none link-secondary opacity-50 hover-opacity-100 transition-all ms-1" data-share-target="composite-index-analysis" aria-haspopup="dialog" aria-label="Share link: Composite Index Analysis"> Share link </button> </h4>Composite indexes require specific query patterns for optimal use: <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-gql" data-lang="gql">PROFILE MATCH (p:Person) WHERE p.city = 'San Francisco' AND p.age > 30 RETURN p; </code></pre></div>Profile output indicates index utilization: <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-fallback" data-lang="fallback">Index Used: Person(city, age) - Full Reasoning: Both predicates match index Rows Examined: 847 Rows Returned: 847 </code></pre></div>If only part of the composite index is used: <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-fallback" data-lang="fallback">Index Used: Person(city, age) - Partial (city only) Reasoning: age predicate not in index-compatible form Rows Examined: 2,341 Rows Returned: 847 </code></pre></div>This indicates optimization opportunity by restructuring the query or index. <h3 id="profiling-join-operations" class="position-relative d-flex align-items-center group"> Profiling Join Operations <button type="button" class="h-share btn btn-link p-0 text-decoration-none link-secondary opacity-50 hover-opacity-100 transition-all ms-1" data-share-target="profiling-join-operations" aria-haspopup="dialog" aria-label="Share link: Profiling Join Operations"> Share link </button> </h3>Graph joins, particularly between multiple patterns, require profiling to optimize join strategies. <h4 id="pattern-join-profiling" class="position-relative d-flex align-items-center group"> Pattern Join Profiling <button type="button" class="h-share btn btn-link p-0 text-decoration-none link-secondary opacity-50 hover-opacity-100 transition-all ms-1" data-share-target="pattern-join-profiling" aria-haspopup="dialog" aria-label="Share link: Pattern Join Profiling"> Share link </button> </h4>Multiple MATCH patterns create implicit joins: <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-gql" data-lang="gql">PROFILE MATCH (p:Person)-[:WORKS_AT]->(c:Company) MATCH (p)-[:LIVES_IN]->(city:City) WHERE c.industry = 'Technology' AND city.name = 'San Francisco' RETURN p.name; </code></pre></div>Profile output shows join execution: <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-fallback" data-lang="fallback">Execution Time: 456.8ms Pattern 1: Person-WORKS_AT->Company Index: Company.industry Rows: 3,421 persons Pattern 2: Person-LIVES_IN->City Index: City.name Rows: 15,234 persons Join Strategy: Hash Join on Person.id Left Input: 3,421 Right Input: 15,234 Join Output: 892 Join Time: 234.5ms </code></pre></div>The join strategy and timing help evaluate whether query restructuring could improve performance. <h3 id="memory-profiling" class="position-relative d-flex align-items-center group"> Memory Profiling <button type="button" class="h-share btn btn-link p-0 text-decoration-none link-secondary opacity-50 hover-opacity-100 transition-all ms-1" data-share-target="memory-profiling" aria-haspopup="dialog" aria-label="Share link: Memory Profiling"> Share link </button> </h3>Understanding memory consumption prevents out-of-memory errors and identifies optimization opportunities. <h4 id="materialization-costs" class="position-relative d-flex align-items-center group"> Materialization Costs <button type="button" class="h-share btn btn-link p-0 text-decoration-none link-secondary opacity-50 hover-opacity-100 transition-all ms-1" data-share-target="materialization-costs" aria-haspopup="dialog" aria-label="Share link: Materialization Costs"> Share link </button> </h4>Some operations require materializing intermediate results: <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-gql" data-lang="gql">PROFILE MATCH (p:Person)-[:KNOWS*2..4]->(connected) RETURN DISTINCT connected.name ORDER BY connected.name; </code></pre></div>Memory profiling reveals: <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-fallback" data-lang="fallback">Execution Time: 3,421ms Peak Memory: 156.7MB Memory Breakdown: - Path Exploration: 89.2MB - Distinct Set: 45.3MB - Sort Buffer: 22.2MB </code></pre></div>Large memory consumption may indicate the need for query restructuring or result streaming. <h4 id="collection-memory-usage" class="position-relative d-flex align-items-center group"> Collection Memory Usage <button type="button" class="h-share btn btn-link p-0 text-decoration-none link-secondary opacity-50 hover-opacity-100 transition-all ms-1" data-share-target="collection-memory-usage" aria-haspopup="dialog" aria-label="Share link: Collection Memory Usage"> Share link </button> </h4>COLLECT operations can consume significant memory: <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-gql" data-lang="gql">PROFILE MATCH (p:Person)-[:PURCHASED]->(product:Product) RETURN p.name, collect(product) AS purchases; </code></pre></div>Memory profiling shows collection sizes: <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-fallback" data-lang="fallback">Collections Created: 8,234 Average Collection Size: 15.6 items Peak Memory: 67.8MB </code></pre></div>If individual collections become very large, consider pagination or limiting collection size. <h3 id="comparative-profiling" class="position-relative d-flex align-items-center group"> Comparative Profiling <button type="button" class="h-share btn btn-link p-0 text-decoration-none link-secondary opacity-50 hover-opacity-100 transition-all ms-1" data-share-target="comparative-profiling" aria-haspopup="dialog" aria-label="Share link: Comparative Profiling"> Share link </button> </h3>Comparing alternative query formulations identifies the most efficient approach. <h4 id="query-variant-comparison" class="position-relative d-flex align-items-center group"> Query Variant Comparison <button type="button" class="h-share btn btn-link p-0 text-decoration-none link-secondary opacity-50 hover-opacity-100 transition-all ms-1" data-share-target="query-variant-comparison" aria-haspopup="dialog" aria-label="Share link: Query Variant Comparison"> Share link </button> </h4>Two queries achieving the same result can have different performance: Version 1: <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-gql" data-lang="gql">PROFILE MATCH (p:Person)-[:KNOWS]->(friend) WHERE friend.city = 'Boston' RETURN p.name, collect(friend.name) AS boston_friends; </code></pre></div>Version 2: <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-gql" data-lang="gql">PROFILE MATCH (p:Person)-[:KNOWS]->(friend:Person) WHERE friend.city = 'Boston' RETURN p.name, [f IN collect(friend) | f.name] AS boston_friends; </code></pre></div>Comparing profile outputs reveals performance differences based on filtering location, collection strategy, and property access patterns. <h3 id="profiling-best-practices" class="position-relative d-flex align-items-center group"> Profiling Best Practices <button type="button" class="h-share btn btn-link p-0 text-decoration-none link-secondary opacity-50 hover-opacity-100 transition-all ms-1" data-share-target="profiling-best-practices" aria-haspopup="dialog" aria-label="Share link: Profiling Best Practices"> Share link </button> </h3>Effective profiling follows systematic approaches. <h4 id="establish-baselines" class="position-relative d-flex align-items-center group"> Establish Baselines <button type="button" class="h-share btn btn-link p-0 text-decoration-none link-secondary opacity-50 hover-opacity-100 transition-all ms-1" data-share-target="establish-baselines" aria-haspopup="dialog" aria-label="Share link: Establish Baselines"> Share link </button> </h4>Before optimization, profile current performance to establish baselines: <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-gql" data-lang="gql">-- Profile current query PROFILE MATCH (p:Person)-[:FRIEND*1..3]->(connected) WHERE p.city = 'Seattle' RETURN count(DISTINCT connected); </code></pre></div>Record baseline metrics: <ul> <li>Execution time: 2,341ms</li> <li>Rows examined: 145,623</li> <li>Memory used: 78.2MB</li> </ul> <h4 id="isolate-variables" class="position-relative d-flex align-items-center group"> Isolate Variables <button type="button" class="h-share btn btn-link p-0 text-decoration-none link-secondary opacity-50 hover-opacity-100 transition-all ms-1" data-share-target="isolate-variables" aria-haspopup="dialog" aria-label="Share link: Isolate Variables"> Share link </button> </h4>When testing optimizations, change one variable at a time: <ol> <li>Profile original query</li> <li>Add index and profile again</li> <li>Compare metrics to isolate index impact</li> <li>Try alternative formulation and profile</li> <li>Compare all variants</li> </ol> <h4 id="profile-representative-data" class="position-relative d-flex align-items-center group"> Profile Representative Data <button type="button" class="h-share btn btn-link p-0 text-decoration-none link-secondary opacity-50 hover-opacity-100 transition-all ms-1" data-share-target="profile-representative-data" aria-haspopup="dialog" aria-label="Share link: Profile Representative Data"> Share link </button> </h4>Always profile against production-like data volumes and distributions. Test data that is too small or too uniform can give misleading profiling results. <h4 id="profile-under-load" class="position-relative d-flex align-items-center group"> Profile Under Load <button type="button" class="h-share btn btn-link p-0 text-decoration-none link-secondary opacity-50 hover-opacity-100 transition-all ms-1" data-share-target="profile-under-load" aria-haspopup="dialog" aria-label="Share link: Profile Under Load"> Share link </button> </h4>Query performance can degrade under concurrent load. Profile in realistic multi-user scenarios: <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"># Run concurrent profiling sessions for i in {1..10}; do ./geode shell < profile_queries.gql & done </code></pre></div> <h3 id="profiling-tools-and-techniques" class="position-relative d-flex align-items-center group"> Profiling Tools and Techniques <button type="button" class="h-share btn btn-link p-0 text-decoration-none link-secondary opacity-50 hover-opacity-100 transition-all ms-1" data-share-target="profiling-tools-and-techniques" aria-haspopup="dialog" aria-label="Share link: Profiling Tools and Techniques"> Share link </button> </h3>Beyond the PROFILE command, additional techniques provide profiling insights. <h4 id="server-side-logging" class="position-relative d-flex align-items-center group"> Server-Side Logging <button type="button" class="h-share btn btn-link p-0 text-decoration-none link-secondary opacity-50 hover-opacity-100 transition-all ms-1" data-share-target="server-side-logging" aria-haspopup="dialog" aria-label="Share link: Server-Side Logging"> Share link </button> </h4>Configure Geode to log slow queries automatically: <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash">geode serve \ --slow-query-log \ --slow-query-threshold 1000 # Log queries >1s </code></pre></div>This captures problematic queries in production without manual profiling. <h4 id="client-side-profiling" class="position-relative d-flex align-items-center group"> Client-Side Profiling <button type="button" class="h-share btn btn-link p-0 text-decoration-none link-secondary opacity-50 hover-opacity-100 transition-all ms-1" data-share-target="client-side-profiling" aria-haspopup="dialog" aria-label="Share link: Client-Side Profiling"> Share link </button> </h4>Client libraries can measure round-trip time: <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-go" data-lang="go">start := time.Now() result, err := conn.Execute(ctx, query) elapsed := time.Since(start) log.Printf("Query took %v", elapsed) </code></pre></div>This includes network latency and client processing, complementing server-side profiling. <h4 id="automated-profiling" class="position-relative d-flex align-items-center group"> Automated Profiling <button type="button" class="h-share btn btn-link p-0 text-decoration-none link-secondary opacity-50 hover-opacity-100 transition-all ms-1" data-share-target="automated-profiling" aria-haspopup="dialog" aria-label="Share link: Automated Profiling"> Share link </button> </h4>Integrate profiling into CI/CD pipelines to detect performance regressions: <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-yaml" data-lang="yaml"># GitLab CI example test_performance: script: - ./run_profile_suite.sh - ./compare_to_baseline.sh artifacts: reports: performance: profile_results.json </code></pre></div> <h3 id="profiling-common-patterns" class="position-relative d-flex align-items-center group"> Profiling Common Patterns <button type="button" class="h-share btn btn-link p-0 text-decoration-none link-secondary opacity-50 hover-opacity-100 transition-all ms-1" data-share-target="profiling-common-patterns" aria-haspopup="dialog" aria-label="Share link: Profiling Common Patterns"> Share link </button> </h3>Certain query patterns have predictable profiling characteristics. <h4 id="hub-node-queries" class="position-relative d-flex align-items-center group"> Hub Node Queries <button type="button" class="h-share btn btn-link p-0 text-decoration-none link-secondary opacity-50 hover-opacity-100 transition-all ms-1" data-share-target="hub-node-queries" aria-haspopup="dialog" aria-label="Share link: Hub Node Queries"> Share link </button> </h4>Queries involving high-degree nodes (hubs) often show performance issues: <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-gql" data-lang="gql">PROFILE MATCH (hub:Person {name: 'Influencer'})-[:FOLLOWS]->(follower) RETURN count(follower); </code></pre></div>Profile output reveals hub impact: <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-fallback" data-lang="fallback">Execution Time: 5,234ms Starting Node Degree: 1,245,678 Followers Traversed: 1,245,678 </code></pre></div>High-degree nodes require special handling, possibly through relationship sampling or pagination. <h4 id="path-finding-queries" class="position-relative d-flex align-items-center group"> Path Finding Queries <button type="button" class="h-share btn btn-link p-0 text-decoration-none link-secondary opacity-50 hover-opacity-100 transition-all ms-1" data-share-target="path-finding-queries" aria-haspopup="dialog" aria-label="Share link: Path Finding Queries"> Share link </button> </h4>Shortest path queries have specific profiling needs: <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-gql" data-lang="gql">PROFILE MATCH path = shortestPath((a:Person {name: 'Alice'})-[:KNOWS*]-(b:Person {name: 'Bob'})) RETURN length(path); </code></pre></div>Profile output shows search efficiency: <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-fallback" data-lang="fallback">Execution Time: 234ms Algorithm: Bidirectional Dijkstra Nodes Explored: 1,247 Path Length: 4 </code></pre></div>The nodes explored metric indicates search efficiency; high exploration suggests sparse connectivity or long paths. <h3 id="optimization-workflow" class="position-relative d-flex align-items-center group"> Optimization Workflow <button type="button" class="h-share btn btn-link p-0 text-decoration-none link-secondary opacity-50 hover-opacity-100 transition-all ms-1" data-share-target="optimization-workflow" aria-haspopup="dialog" aria-label="Share link: Optimization Workflow"> Share link </button> </h3>Profiling drives a systematic optimization workflow. <h4 id="step-1-profile-current-state" class="position-relative d-flex align-items-center group"> Step 1: Profile Current State <button type="button" class="h-share btn btn-link p-0 text-decoration-none link-secondary opacity-50 hover-opacity-100 transition-all ms-1" data-share-target="step-1-profile-current-state" aria-haspopup="dialog" aria-label="Share link: Step 1: Profile Current State"> Share link </button> </h4><div class="highlight"><pre tabindex="0" class="chroma"><code class="language-gql" data-lang="gql">PROFILE [your query] </code></pre></div>Document baseline metrics comprehensively. <h4 id="step-2-identify-bottlenecks" class="position-relative d-flex align-items-center group"> Step 2: Identify Bottlenecks <button type="button" class="h-share btn btn-link p-0 text-decoration-none link-secondary opacity-50 hover-opacity-100 transition-all ms-1" data-share-target="step-2-identify-bottlenecks" aria-haspopup="dialog" aria-label="Share link: Step 2: Identify Bottlenecks"> Share link </button> </h4>Analyze profile output to find: <ul> <li>Longest-running operations</li> <li>Highest row examination counts</li> <li>Memory pressure points</li> <li>Missing index usage</li> </ul> <h4 id="step-3-hypothesize-improvements" class="position-relative d-flex align-items-center group"> Step 3: Hypothesize Improvements <button type="button" class="h-share btn btn-link p-0 text-decoration-none link-secondary opacity-50 hover-opacity-100 transition-all ms-1" data-share-target="step-3-hypothesize-improvements" aria-haspopup="dialog" aria-label="Share link: Step 3: Hypothesize Improvements"> Share link </button> </h4>Based on bottlenecks, form specific hypotheses: <ul> <li>“Adding an index on Person.age would reduce scan time”</li> <li>“Limiting traversal depth would reduce explored paths”</li> <li>“Filtering earlier would reduce intermediate results”</li> </ul> <h4 id="step-4-test-hypotheses" class="position-relative d-flex align-items-center group"> Step 4: Test Hypotheses <button type="button" class="h-share btn btn-link p-0 text-decoration-none link-secondary opacity-50 hover-opacity-100 transition-all ms-1" data-share-target="step-4-test-hypotheses" aria-haspopup="dialog" aria-label="Share link: Step 4: Test Hypotheses"> Share link </button> </h4>Implement one change and profile again: <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-gql" data-lang="gql">-- Create index CREATE INDEX ON Person(age); -- Profile again PROFILE MATCH (n:Person) WHERE n.age > 30 RETURN n.name, n.age; </code></pre></div> <h4 id="step-5-compare-results" class="position-relative d-flex align-items-center group"> Step 5: Compare Results <button type="button" class="h-share btn btn-link p-0 text-decoration-none link-secondary opacity-50 hover-opacity-100 transition-all ms-1" data-share-target="step-5-compare-results" aria-haspopup="dialog" aria-label="Share link: Step 5: Compare Results"> Share link </button> </h4>Compare new profile to baseline to quantify improvement. <h4 id="step-6-iterate" class="position-relative d-flex align-items-center group"> Step 6: Iterate <button type="button" class="h-share btn btn-link p-0 text-decoration-none link-secondary opacity-50 hover-opacity-100 transition-all ms-1" data-share-target="step-6-iterate" aria-haspopup="dialog" aria-label="Share link: Step 6: Iterate"> Share link </button> </h4>Continue identifying bottlenecks and testing improvements until performance meets requirements. <h3 id="advanced-profiling-techniques" class="position-relative d-flex align-items-center group"> Advanced Profiling Techniques <button type="button" class="h-share btn btn-link p-0 text-decoration-none link-secondary opacity-50 hover-opacity-100 transition-all ms-1" data-share-target="advanced-profiling-techniques" aria-haspopup="dialog" aria-label="Share link: Advanced Profiling Techniques"> Share link </button> </h3>Expert-level profiling goes beyond basic PROFILE commands. <h4 id="profiling-sub-queries" class="position-relative d-flex align-items-center group"> Profiling Sub-Queries <button type="button" class="h-share btn btn-link p-0 text-decoration-none link-secondary opacity-50 hover-opacity-100 transition-all ms-1" data-share-target="profiling-sub-queries" aria-haspopup="dialog" aria-label="Share link: Profiling Sub-Queries"> Share link </button> </h4>Complex queries with sub-queries require profiling at multiple levels: <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-gql" data-lang="gql">PROFILE MATCH (p:Person) WHERE p.age > ( MATCH (p2:Person) RETURN avg(p2.age) ) RETURN p.name; </code></pre></div>Profile output breaks down main query and sub-query execution separately. <h4 id="profiling-with-clauses" class="position-relative d-flex align-items-center group"> Profiling WITH Clauses <button type="button" class="h-share btn btn-link p-0 text-decoration-none link-secondary opacity-50 hover-opacity-100 transition-all ms-1" data-share-target="profiling-with-clauses" aria-haspopup="dialog" aria-label="Share link: Profiling WITH Clauses"> Share link </button> </h4>WITH clauses create query pipelines; profile each stage: <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-gql" data-lang="gql">PROFILE MATCH (p:Person)-[:PURCHASED]->(prod:Product) WITH p, count(prod) AS purchase_count WHERE purchase_count > 10 MATCH (p)-[:LIVES_IN]->(city:City) RETURN city.name, count(p) AS high_value_customers; </code></pre></div>Profile output shows execution time and row counts at each WITH boundary. <h3 id="related-topics" class="position-relative d-flex align-items-center group"> Related Topics <button type="button" class="h-share btn btn-link p-0 text-decoration-none link-secondary opacity-50 hover-opacity-100 transition-all ms-1" data-share-target="related-topics" aria-haspopup="dialog" aria-label="Share link: Related Topics"> Share link </button> </h3>Performance profiling connects to several related areas: <ul> <li>Performance Tuning - Applying profiling insights to optimize configuration</li> <li>Query Optimization - Restructuring queries based on profiling data</li> <li>Index Management - Creating indexes informed by profiling analysis</li> <li>Monitoring - Continuous profiling in production environments</li> <li>Troubleshooting - Using profiling to diagnose performance issues</li> </ul> <h3 id="resources" class="position-relative d-flex align-items-center group"> Resources <button type="button" class="h-share btn btn-link p-0 text-decoration-none link-secondary opacity-50 hover-opacity-100 transition-all ms-1" data-share-target="resources" aria-haspopup="dialog" aria-label="Share link: Resources"> Share link </button> </h3>Additional profiling resources: <ul> <li>Geode PROFILE command documentation with complete syntax reference</li> <li>Query optimization guides with profiling-driven examples</li> <li>Performance benchmarking methodologies for graph databases</li> <li>ISO/IEC 39075:2024 GQL standard profiling facilities</li> </ul> Performance profiling transforms database optimization from guesswork into an evidence-based engineering discipline. By systematically measuring query execution characteristics, developers can make informed decisions that demonstrably improve application performance and user experience.

Popular

Related Articles

Query Profiling Guide

Query Profiling with EXPLAIN and PROFILE