Query Profiling with EXPLAIN and PROFILE

<h3 id="overview" class="position-relative d-flex align-items-center group"> Overview <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="overview" aria-haspopup="dialog" aria-label="Share link: Overview"> 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>Geode provides two powerful commands for understanding and optimizing query execution: EXPLAIN and PROFILE. These tools are essential for query optimization, performance tuning, and understanding how Geode processes your graph queries. <h4 id="what-youll-learn" class="position-relative d-flex align-items-center group"> What You&rsquo;ll Learn <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="what-youll-learn" aria-haspopup="dialog" aria-label="Share link: What Youll Learn"> Share link </button> </h4><ul> <li>How to use EXPLAIN to view execution plans without running queries</li> <li>How to use PROFILE to measure actual query performance</li> <li>Understanding execution plan operators and their meaning</li> <li>Identifying performance bottlenecks using profiling metrics</li> <li>Best practices for query optimization based on analysis results</li> </ul> <h4 id="prerequisites" class="position-relative d-flex align-items-center group"> Prerequisites <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="prerequisites" aria-haspopup="dialog" aria-label="Share link: Prerequisites"> Share link </button> </h4><ul> <li>Geode server running (see <a href="/guides/installation/" >Installation Guide</a> )</li> <li>Basic familiarity with <a href="/docs/gql/guide/" >GQL syntax</a> </li> <li>Understanding of <a href="/docs/model/data-model-and-types/" >graph data models</a> </li> </ul> <hr> <h3 id="explain-command" class="position-relative d-flex align-items-center group"> EXPLAIN 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="explain-command" aria-haspopup="dialog" aria-label="Share link: EXPLAIN Command"> Share link </button> </h3>The EXPLAIN command displays the query execution plan without actually executing the query. This is useful for understanding how Geode will process a query before committing to the execution. <h4 id="basic-syntax" class="position-relative d-flex align-items-center group"> Basic Syntax <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-syntax" aria-haspopup="dialog" aria-label="Share link: Basic Syntax"> Share link </button> </h4><div class="highlight"><pre tabindex="0" class="chroma"><code class="language-gql" data-lang="gql">EXPLAIN <statement> </code></pre></div> <h4 id="how-it-works" class="position-relative d-flex align-items-center group"> How It Works <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="how-it-works" aria-haspopup="dialog" aria-label="Share link: How It Works"> Share link </button> </h4>When you prefix a query with <code>EXPLAIN</code>, Geode: <ol> <li>Parses the query to build an Abstract Syntax Tree (AST)</li> <li>Generates a logical execution plan</li> <li>Returns a textual representation of the plan</li> <li>Does not execute the query or access data</li> </ol> This makes EXPLAIN a zero-cost operation perfect for exploring query strategies. <hr> <h3 id="explain-examples" class="position-relative d-flex align-items-center group"> EXPLAIN Examples <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="explain-examples" aria-haspopup="dialog" aria-label="Share link: EXPLAIN Examples"> Share link </button> </h3> <h4 id="simple-match-query" class="position-relative d-flex align-items-center group"> Simple MATCH Query <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-match-query" aria-haspopup="dialog" aria-label="Share link: Simple MATCH Query"> Share link </button> </h4><div class="highlight"><pre tabindex="0" class="chroma"><code class="language-gql" data-lang="gql">EXPLAIN MATCH (p:Person) RETURN p.name </code></pre></div>Output: <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-fallback" data-lang="fallback">| plan | |-------------------| | EXPLAIN | | MATCH | | NodeScan | | RETURN | | Project | </code></pre></div>Interpretation: <ul> <li><code>NodeScan</code>: Scans all nodes with the <code>Person</code> label</li> <li><code>Project</code>: Selects and transforms <code>p.name</code> for the RETURN clause</li> </ul> <h4 id="match-with-where-clause" class="position-relative d-flex align-items-center group"> MATCH with WHERE Clause <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="match-with-where-clause" aria-haspopup="dialog" aria-label="Share link: MATCH with WHERE Clause"> Share link </button> </h4><div class="highlight"><pre tabindex="0" class="chroma"><code class="language-gql" data-lang="gql">EXPLAIN MATCH (p:Person) WHERE p.age > 25 RETURN p.name, p.age </code></pre></div>Output: <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-fallback" data-lang="fallback">| plan | |-------------------| | EXPLAIN | | MATCH | | NodeScan | | Filter | | RETURN | | Project | </code></pre></div>New Operator: <ul> <li><code>Filter</code>: Applies the <code>WHERE p.age > 25</code> predicate to filter results</li> </ul> <h4 id="relationship-traversal" class="position-relative d-flex align-items-center group"> Relationship Traversal <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="relationship-traversal" aria-haspopup="dialog" aria-label="Share link: Relationship Traversal"> Share link </button> </h4><div class="highlight"><pre tabindex="0" class="chroma"><code class="language-gql" data-lang="gql">EXPLAIN MATCH (p:Person)-[:WORKS_FOR]->(c:Company) RETURN p.name, c.name </code></pre></div>Output: <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-fallback" data-lang="fallback">| plan | |-------------------------| | EXPLAIN | | MATCH | | NodeScan | | ExpandRelationships | | RETURN | | Project | </code></pre></div>New Operator: <ul> <li><code>ExpandRelationships</code>: Traverses <code>WORKS_FOR</code> relationships from <code>Person</code> nodes</li> </ul> <h4 id="complex-query-with-aggregation" class="position-relative d-flex align-items-center group"> Complex Query with Aggregation <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-query-with-aggregation" aria-haspopup="dialog" aria-label="Share link: Complex Query with Aggregation"> Share link </button> </h4><div class="highlight"><pre tabindex="0" class="chroma"><code class="language-gql" data-lang="gql">EXPLAIN MATCH (p:Person)-[:WORKS_FOR]->(c:Company) WHERE p.age > 25 RETURN c.name, count(p) AS employee_count ORDER BY employee_count DESC LIMIT 10 </code></pre></div>Output: <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-fallback" data-lang="fallback">| plan | |-------------------------| | EXPLAIN | | MATCH | | NodeScan | | ExpandRelationships | | Filter | | RETURN | | Aggregate | | Project | | Sort | | Limit | </code></pre></div>Additional Operators: <ul> <li><code>Aggregate</code>: Groups by <code>c.name</code> and computes <code>count(p)</code></li> <li><code>Sort</code>: Orders results by <code>employee_count DESC</code></li> <li><code>Limit</code>: Restricts output to 10 rows</li> </ul> <hr> <h3 id="understanding-execution-plan-operators" class="position-relative d-flex align-items-center group"> Understanding Execution Plan Operators <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-execution-plan-operators" aria-haspopup="dialog" aria-label="Share link: Understanding Execution Plan Operators"> Share link </button> </h3> <h4 id="core-operators" class="position-relative d-flex align-items-center group"> Core Operators <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="core-operators" aria-haspopup="dialog" aria-label="Share link: Core Operators"> Share link </button> </h4><table> <thead> <tr> <th>Operator</th> <th>Description</th> <th>When Used</th> </tr> </thead> <tbody> <tr> <td>NodeScan</td> <td>Scans all nodes (or nodes matching a label)</td> <td>Every MATCH clause</td> </tr> <tr> <td>ExpandRelationships</td> <td>Traverses relationships from source nodes</td> <td>Relationship patterns <code>()-[]->()</code></td> </tr> <tr> <td>Filter</td> <td>Applies WHERE clause predicates</td> <td>Queries with WHERE conditions</td> </tr> <tr> <td>Project</td> <td>Selects and transforms columns for RETURN</td> <td>All queries with RETURN</td> </tr> <tr> <td>Sort</td> <td>Orders results</td> <td>Queries with ORDER BY</td> </tr> <tr> <td>Limit</td> <td>Restricts output rows</td> <td>Queries with LIMIT</td> </tr> <tr> <td>Aggregate</td> <td>Groups and aggregates data</td> <td>Aggregation functions (COUNT, SUM, etc.)</td> </tr> </tbody> </table> <h4 id="data-modification-operators" class="position-relative d-flex align-items-center group"> Data Modification Operators <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="data-modification-operators" aria-haspopup="dialog" aria-label="Share link: Data Modification Operators"> Share link </button> </h4><table> <thead> <tr> <th>Operator</th> <th>Description</th> <th>Statement Type</th> </tr> </thead> <tbody> <tr> <td>CreateNodes</td> <td>Creates new nodes</td> <td>CREATE</td> </tr> <tr> <td>CreateRelationships</td> <td>Creates new relationships</td> <td>CREATE</td> </tr> <tr> <td>DeleteNodes</td> <td>Deletes nodes</td> <td>DELETE, DETACH DELETE</td> </tr> <tr> <td>ExecuteStatement</td> <td>Generic execution wrapper</td> <td>MERGE, SET, REMOVE</td> </tr> </tbody> </table> <hr> <h3 id="explain-for-different-statement-types" class="position-relative d-flex align-items-center group"> EXPLAIN for Different Statement Types <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="explain-for-different-statement-types" aria-haspopup="dialog" aria-label="Share link: EXPLAIN for Different Statement Types"> Share link </button> </h3> <h4 id="create-statement" class="position-relative d-flex align-items-center group"> CREATE Statement <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="create-statement" aria-haspopup="dialog" aria-label="Share link: CREATE Statement"> Share link </button> </h4><div class="highlight"><pre tabindex="0" class="chroma"><code class="language-gql" data-lang="gql">EXPLAIN CREATE (p:Person {name: 'Alice', age: 30}) </code></pre></div>Output: <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-fallback" data-lang="fallback">| plan | |-------------------------| | EXPLAIN | | CREATE | | CreateNodes | | CreateRelationships | </code></pre></div> <h4 id="delete-statement" class="position-relative d-flex align-items-center group"> DELETE Statement <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="delete-statement" aria-haspopup="dialog" aria-label="Share link: DELETE Statement"> Share link </button> </h4><div class="highlight"><pre tabindex="0" class="chroma"><code class="language-gql" data-lang="gql">EXPLAIN MATCH (p:Person) WHERE p.temp = true DELETE p </code></pre></div>Output: <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-fallback" data-lang="fallback">| plan | |-------------------------| | EXPLAIN | | DELETE | | DeleteNodes | </code></pre></div> <h4 id="merge-statement" class="position-relative d-flex align-items-center group"> MERGE Statement <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="merge-statement" aria-haspopup="dialog" aria-label="Share link: MERGE Statement"> Share link </button> </h4><div class="highlight"><pre tabindex="0" class="chroma"><code class="language-gql" data-lang="gql">EXPLAIN MERGE (p:Person {email: 'user@example.com'}) ON CREATE SET p.created = datetime() ON MATCH SET p.accessed = now() </code></pre></div>Output: <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-fallback" data-lang="fallback">| plan | |-------------------------| | EXPLAIN | | ExecuteStatement | </code></pre></div>Note: MERGE operations show <code>ExecuteStatement</code> as they combine MATCH, CREATE, and SET logic. <hr> <h3 id="profile-command" class="position-relative d-flex align-items-center group"> 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="profile-command" aria-haspopup="dialog" aria-label="Share link: PROFILE Command"> Share link </button> </h3>The PROFILE command executes a query and returns execution statistics. Unlike EXPLAIN, PROFILE actually runs the query and provides real metrics about the execution. <h4 id="basic-syntax-1" class="position-relative d-flex align-items-center group"> Basic Syntax <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-syntax-1" aria-haspopup="dialog" aria-label="Share link: Basic Syntax"> Share link </button> </h4><div class="highlight"><pre tabindex="0" class="chroma"><code class="language-gql" data-lang="gql">PROFILE <statement> </code></pre></div> <h4 id="how-it-works-1" class="position-relative d-flex align-items-center group"> How It Works <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="how-it-works-1" aria-haspopup="dialog" aria-label="Share link: How It Works"> Share link </button> </h4>When you prefix a query with <code>PROFILE</code>, Geode: <ol> <li>Executes the query normally</li> <li>Collects execution metrics (rows returned, execution time, column count)</li> <li>Returns statistics as a result set</li> <li>Does execute the query (results are generated but not returned)</li> </ol> <hr> <h3 id="profile-examples" class="position-relative d-flex align-items-center group"> PROFILE Examples <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-examples" aria-haspopup="dialog" aria-label="Share link: PROFILE Examples"> Share link </button> </h3> <h4 id="simple-query-profiling" class="position-relative d-flex align-items-center group"> Simple Query 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-query-profiling" aria-haspopup="dialog" aria-label="Share link: Simple Query Profiling"> Share link </button> </h4><div class="highlight"><pre tabindex="0" class="chroma"><code class="language-gql" data-lang="gql">PROFILE MATCH (p:Person) RETURN p.name </code></pre></div>Output: <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-fallback" data-lang="fallback">| metric | value | |---------------------|-------| | rows_returned | 42 | | columns | 1 | | execution_time_ms | 1 | </code></pre></div>Metrics Explained: <ul> <li><code>rows_returned</code>: Number of rows returned by the query (42 Person nodes)</li> <li><code>columns</code>: Number of columns in the result set (1: <code>p.name</code>)</li> <li><code>execution_time_ms</code>: Execution time in milliseconds (placeholder in current implementation)</li> </ul> <h4 id="profiling-with-aggregation" class="position-relative d-flex align-items-center group"> Profiling with Aggregation <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-aggregation" aria-haspopup="dialog" aria-label="Share link: Profiling with Aggregation"> Share link </button> </h4><div class="highlight"><pre tabindex="0" class="chroma"><code class="language-gql" data-lang="gql">PROFILE MATCH (p:Person) RETURN count(p) AS person_count </code></pre></div>Output: <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-fallback" data-lang="fallback">| metric | value | |---------------------|-------| | rows_returned | 1 | | columns | 1 | | execution_time_ms | 1 | </code></pre></div>Observation: Aggregation queries return a single row with the aggregated value. <h4 id="profiling-complex-queries" class="position-relative d-flex align-items-center group"> Profiling Complex 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-complex-queries" aria-haspopup="dialog" aria-label="Share link: Profiling Complex Queries"> Share link </button> </h4><div class="highlight"><pre tabindex="0" class="chroma"><code class="language-gql" data-lang="gql">PROFILE MATCH (p:Person)-[:WORKS_FOR]->(c:Company) WHERE c.industry = 'Technology' RETURN p.name, c.name </code></pre></div>Output: <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-fallback" data-lang="fallback">| metric | value | |---------------------|-------| | rows_returned | 156 | | columns | 2 | | execution_time_ms | 1 | </code></pre></div>Metrics: <ul> <li><code>rows_returned</code>: 156 Person-Company pairs in the Technology industry</li> <li><code>columns</code>: 2 (<code>p.name</code>, <code>c.name</code>)</li> </ul> <h4 id="profiling-empty-results" class="position-relative d-flex align-items-center group"> Profiling Empty 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="profiling-empty-results" aria-haspopup="dialog" aria-label="Share link: Profiling Empty Results"> Share link </button> </h4><div class="highlight"><pre tabindex="0" class="chroma"><code class="language-gql" data-lang="gql">PROFILE MATCH (p:NonExistent) RETURN p </code></pre></div>Output: <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-fallback" data-lang="fallback">| metric | value | |---------------------|-------| | rows_returned | 0 | | columns | 1 | | execution_time_ms | 1 | </code></pre></div>Note: Zero rows returned but column structure is still defined. <hr> <h3 id="performance-analysis-workflow" class="position-relative d-flex align-items-center group"> Performance Analysis 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="performance-analysis-workflow" aria-haspopup="dialog" aria-label="Share link: Performance Analysis Workflow"> Share link </button> </h3> <h4 id="step-1-understand-the-plan-with-explain" class="position-relative d-flex align-items-center group"> Step 1: Understand the Plan with EXPLAIN <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-understand-the-plan-with-explain" aria-haspopup="dialog" aria-label="Share link: Step 1: Understand the Plan with EXPLAIN"> Share link </button> </h4>Before running an expensive query, use EXPLAIN to understand the execution strategy: <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-gql" data-lang="gql">EXPLAIN MATCH (p:Person)-[:KNOWS*1..3]->(friend:Person) WHERE p.age > 30 RETURN friend.name ORDER BY friend.name LIMIT 100 </code></pre></div>Analysis Questions: <ul> <li>Are indexes being used? (Look for index scan operators)</li> <li>Is filtering applied early? (<code>Filter</code> should appear after <code>NodeScan</code>)</li> <li>Are expensive operations (like variable-length paths) necessary?</li> </ul> <h4 id="step-2-measure-performance-with-profile" class="position-relative d-flex align-items-center group"> Step 2: Measure Performance with PROFILE <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-measure-performance-with-profile" aria-haspopup="dialog" aria-label="Share link: Step 2: Measure Performance with PROFILE"> Share link </button> </h4>Execute the query with PROFILE to gather real metrics: <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-gql" data-lang="gql">PROFILE MATCH (p:Person)-[:KNOWS*1..3]->(friend:Person) WHERE p.age > 30 RETURN friend.name ORDER BY friend.name LIMIT 100 </code></pre></div>Metrics to Check: <ul> <li><code>rows_returned</code>: Validate the result set size</li> <li><code>execution_time_ms</code>: Measure actual execution time (future enhancement)</li> </ul> <h4 id="step-3-compare-approaches" class="position-relative d-flex align-items-center group"> Step 3: Compare Approaches <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-compare-approaches" aria-haspopup="dialog" aria-label="Share link: Step 3: Compare Approaches"> Share link </button> </h4>Test different query formulations and compare their performance: Approach 1: Filter in WHERE <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-gql" data-lang="gql">PROFILE MATCH (p:Person) WHERE p.age > 30 RETURN p.name </code></pre></div>Approach 2: Filter with Label Test <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-gql" data-lang="gql">PROFILE MATCH (n) WHERE n:Person AND n.age > 30 RETURN n.name </code></pre></div>Compare <code>rows_returned</code> and adjust based on results. <hr> <h3 id="common-optimization-patterns" class="position-relative d-flex align-items-center group"> Common Optimization 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="common-optimization-patterns" aria-haspopup="dialog" aria-label="Share link: Common Optimization Patterns"> Share link </button> </h3> <h4 id="pattern-1-index-selection-verification" class="position-relative d-flex align-items-center group"> Pattern 1: Index Selection Verification <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-1-index-selection-verification" aria-haspopup="dialog" aria-label="Share link: Pattern 1: Index Selection Verification"> Share link </button> </h4>Problem: Unsure if an index is being used. Solution: Use EXPLAIN to check for index scan operators (future enhancement). <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-gql" data-lang="gql">-- Without index EXPLAIN MATCH (p:Person {email: 'user@example.com'}) RETURN p -- After creating index -- CREATE INDEX ON :Person(email) EXPLAIN MATCH (p:Person {email: 'user@example.com'}) RETURN p </code></pre></div>Expected Change: Look for <code>IndexScan</code> instead of <code>NodeScan</code> (future enhancement). <h4 id="pattern-2-filter-ordering" class="position-relative d-flex align-items-center group"> Pattern 2: Filter Ordering <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-2-filter-ordering" aria-haspopup="dialog" aria-label="Share link: Pattern 2: Filter Ordering"> Share link </button> </h4>Problem: Expensive filters applied too late. Solution: Ensure filters appear early in the execution plan. <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-gql" data-lang="gql">EXPLAIN MATCH (p:Person)-[:KNOWS]->(f:Person) WHERE p.age > 25 AND f.age > 25 RETURN p.name, f.name </code></pre></div>Good Plan: <code>Filter</code> appears right after <code>NodeScan</code> before <code>ExpandRelationships</code>. <h4 id="pattern-3-pagination-impact" class="position-relative d-flex align-items-center group"> Pattern 3: Pagination Impact <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-3-pagination-impact" aria-haspopup="dialog" aria-label="Share link: Pattern 3: Pagination Impact"> Share link </button> </h4>Problem: Expensive ORDER BY with large result sets. Solution: Use LIMIT to reduce the cost of sorting. <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-gql" data-lang="gql">-- Expensive: Sort all results PROFILE MATCH (p:Person) RETURN p.name ORDER BY p.name -- Efficient: Sort only top 100 PROFILE MATCH (p:Person) RETURN p.name ORDER BY p.name LIMIT 100 </code></pre></div>Comparison: Second query should return the same columns but with fewer <code>rows_returned</code> if the table has more than 100 rows. <hr> <h3 id="implementation-details" class="position-relative d-flex align-items-center group"> Implementation Details <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="implementation-details" aria-haspopup="dialog" aria-label="Share link: Implementation Details"> Share link </button> </h3> <h4 id="parser-implementation" class="position-relative d-flex align-items-center group"> Parser Implementation <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="parser-implementation" aria-haspopup="dialog" aria-label="Share link: Parser Implementation"> Share link </button> </h4>Both EXPLAIN and PROFILE are parsed as top-level statements that wrap another statement: <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-zig" data-lang="zig">// From parser.zig:2554-2572 fn parseExplainStatement(self: *Parser) ParserError!ast.Statement { _ = try self.expect(.EXPLAIN); const query_stmt_ptr = try self.arena.allocator().create(ast.Statement); query_stmt_ptr.* = try self.parseStatement(); return .{ .Explain = .{ .query = query_stmt_ptr } }; } fn parseProfileStatement(self: *Parser) ParserError!ast.Statement { _ = try self.expect(.PROFILE); const query_stmt_ptr = try self.arena.allocator().create(ast.Statement); query_stmt_ptr.* = try self.parseStatement(); return .{ .Profile = .{ .query = query_stmt_ptr } }; } </code></pre></div> <h4 id="ast-structures" class="position-relative d-flex align-items-center group"> AST Structures <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="ast-structures" aria-haspopup="dialog" aria-label="Share link: AST Structures"> Share link </button> </h4><div class="highlight"><pre tabindex="0" class="chroma"><code class="language-zig" data-lang="zig">// From ast.zig:46-47 pub const Statement = union(enum) { // ... other statements ... Explain: ExplainStatement, Profile: ProfileStatement, // ... other statements ... }; pub const ExplainStatement = struct { query: *Statement, }; pub const ProfileStatement = struct { query: *Statement, }; </code></pre></div> <h4 id="execution-logic" class="position-relative d-flex align-items-center group"> Execution Logic <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="execution-logic" aria-haspopup="dialog" aria-label="Share link: Execution Logic"> Share link </button> </h4>EXPLAIN Execution (<code>execution.zig:863-940</code>): <ul> <li>Analyzes the wrapped statement structure</li> <li>Generates a plan description based on query type</li> <li>Returns plan as a result set with a single <code>plan</code> column</li> </ul> PROFILE Execution (<code>execution.zig:942-988</code>): <ul> <li>Executes the wrapped query using <code>executeStatementWithContext</code></li> <li>Collects metrics (rows returned, column count)</li> <li>Returns statistics as a result set with <code>metric</code> and <code>value</code> columns</li> </ul> <hr> <h3 id="use-cases" class="position-relative d-flex align-items-center group"> Use Cases <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="use-cases" aria-haspopup="dialog" aria-label="Share link: Use Cases"> Share link </button> </h3> <h4 id="use-case-1-query-optimization" class="position-relative d-flex align-items-center group"> Use Case 1: Query Optimization <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="use-case-1-query-optimization" aria-haspopup="dialog" aria-label="Share link: Use Case 1: Query Optimization"> Share link </button> </h4>Scenario: Optimize a slow query before deploying to production. <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-gql" data-lang="gql">-- Step 1: Understand execution plan EXPLAIN MATCH (p:Person)-[:WORKS_FOR]->(c:Company) WHERE c.name = 'Acme Corp' RETURN p.name -- Step 2: Check if index would help -- CREATE INDEX ON :Company(name) -- Step 3: Re-check plan EXPLAIN MATCH (p:Person)-[:WORKS_FOR]->(c:Company) WHERE c.name = 'Acme Corp' RETURN p.name -- Step 4: Measure improvement PROFILE MATCH (p:Person)-[:WORKS_FOR]->(c:Company) WHERE c.name = 'Acme Corp' RETURN p.name </code></pre></div> <h4 id="use-case-2-understanding-behavior" class="position-relative d-flex align-items-center group"> Use Case 2: Understanding Behavior <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="use-case-2-understanding-behavior" aria-haspopup="dialog" aria-label="Share link: Use Case 2: Understanding Behavior"> Share link </button> </h4>Scenario: Understand how Geode processes a complex path query. <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-gql" data-lang="gql">EXPLAIN MATCH (p:Person) WHERE p.age > 30 OR p.department = 'Engineering' RETURN p.name, p.age ORDER BY p.age DESC LIMIT 50 </code></pre></div>Analysis: <ul> <li>Check that <code>Filter</code> is applied before expensive operations</li> <li>Verify <code>Sort</code> and <code>Limit</code> operators are present</li> <li>Understand the logical flow: Scan → Filter → Project → Sort → Limit</li> </ul> <h4 id="use-case-3-performance-tuning" class="position-relative d-flex align-items-center group"> Use Case 3: Performance Tuning <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="use-case-3-performance-tuning" aria-haspopup="dialog" aria-label="Share link: Use Case 3: Performance Tuning"> Share link </button> </h4>Scenario: Identify which part of a query is slow. <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-gql" data-lang="gql">-- Measure overall performance PROFILE MATCH (a:Person)-[:KNOWS]->(b:Person)-[:KNOWS]->(c:Person) WHERE a.name = 'Alice' RETURN c.name -- Check execution plan EXPLAIN MATCH (a:Person)-[:KNOWS]->(b:Person)-[:KNOWS]->(c:Person) WHERE a.name = 'Alice' RETURN c.name </code></pre></div>Optimization Strategy: <ul> <li>If <code>rows_returned</code> is very high, consider adding more WHERE clauses</li> <li>If multiple <code>ExpandRelationships</code> operators are expensive, consider indexing relationships</li> </ul> <hr> <h3 id="best-practices" class="position-relative d-flex align-items-center group"> 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="best-practices" aria-haspopup="dialog" aria-label="Share link: Best Practices"> Share link </button> </h3> <h4 id="when-to-use-explain" class="position-relative d-flex align-items-center group"> When to Use EXPLAIN <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="when-to-use-explain" aria-haspopup="dialog" aria-label="Share link: When to Use EXPLAIN"> Share link </button> </h4>✅ Use EXPLAIN when: <ul> <li>Developing new queries and want to understand the execution strategy</li> <li>Verifying that indexes are being used (when index operators are available)</li> <li>Comparing different query formulations before choosing one</li> <li>Learning how Geode processes different query patterns</li> <li>Checking query plans for queries that will run frequently</li> </ul> ❌ Don’t use EXPLAIN when: <ul> <li>You need actual performance metrics (use PROFILE instead)</li> <li>You need to see actual query results (run the query normally)</li> </ul> <h4 id="when-to-use-profile" class="position-relative d-flex align-items-center group"> When to Use PROFILE <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="when-to-use-profile" aria-haspopup="dialog" aria-label="Share link: When to Use PROFILE"> Share link </button> </h4>✅ Use PROFILE when: <ul> <li>Measuring actual query performance</li> <li>Validating optimization changes (before/after comparison)</li> <li>Identifying slow queries in development</li> <li>Understanding result set sizes before running expensive queries</li> <li>Testing pagination and limit strategies</li> </ul> ❌ Don’t use PROFILE when: <ul> <li>You want to avoid executing the query (use EXPLAIN instead)</li> <li>Running queries with side effects (CREATE, DELETE, SET)—results will be committed</li> </ul> <h4 id="combining-both-commands" class="position-relative d-flex align-items-center group"> Combining Both Commands <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="combining-both-commands" aria-haspopup="dialog" aria-label="Share link: Combining Both Commands"> Share link </button> </h4>Best Practice: Use EXPLAIN first, then PROFILE. <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-gql" data-lang="gql">-- 1. Understand the plan EXPLAIN MATCH (p:Person) WHERE p.age > 30 RETURN p.name -- 2. Measure performance PROFILE MATCH (p:Person) WHERE p.age > 30 RETURN p.name -- 3. Run the actual query MATCH (p:Person) WHERE p.age > 30 RETURN p.name </code></pre></div><hr> <h3 id="current-limitations" class="position-relative d-flex align-items-center group"> Current Limitations <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="current-limitations" aria-haspopup="dialog" aria-label="Share link: Current Limitations"> Share link </button> </h3> <h4 id="explain-limitations" class="position-relative d-flex align-items-center group"> EXPLAIN Limitations <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="explain-limitations" aria-haspopup="dialog" aria-label="Share link: EXPLAIN Limitations"> Share link </button> </h4><ol> <li>Simplified Plans: Shows logical operators but not detailed cost estimates</li> <li>No Index Information: Plans don’t currently show which indexes are used</li> <li>No Row Estimates: No estimated row counts per operator</li> <li>Limited Detail: No per-operator statistics or memory usage</li> </ol> <h4 id="profile-limitations" class="position-relative d-flex align-items-center group"> PROFILE Limitations <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-limitations" aria-haspopup="dialog" aria-label="Share link: PROFILE Limitations"> Share link </button> </h4><ol> <li>Placeholder Timing: <code>execution_time_ms</code> is currently a placeholder (always returns 1)</li> <li>No Operator Breakdown: Doesn’t show per-operator metrics</li> <li>No Memory Usage: Memory consumption not tracked</li> <li>Limited Metrics: Only rows, columns, and execution time (placeholder)</li> </ol> <hr> <h3 id="future-enhancements" class="position-relative d-flex align-items-center group"> Future Enhancements <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="future-enhancements" aria-haspopup="dialog" aria-label="Share link: Future Enhancements"> Share link </button> </h3> <h4 id="planned-improvements" class="position-relative d-flex align-items-center group"> Planned 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="planned-improvements" aria-haspopup="dialog" aria-label="Share link: Planned Improvements"> Share link </button> </h4>EXPLAIN Enhancements: <ul> <li>Cost-Based Plans: Include estimated costs and row counts per operator</li> <li>Index Usage: Show which indexes are being used in the plan</li> <li>Visual Plans: Tree or graph visualization of query plans</li> <li>Warnings: Detect and warn about potential performance issues (e.g., missing indexes)</li> <li>Comparison Mode: Compare plans for different query formulations side-by-side</li> </ul> PROFILE Enhancements: <ul> <li>Actual Timing: Real execution time measurements with high precision</li> <li>Per-Operator Stats: Detailed metrics for each operator (rows processed, time spent)</li> <li>Memory Profiling: Track memory allocation and usage during execution</li> <li>Cache Statistics: Show index and data cache hit/miss ratios</li> <li>I/O Metrics: Track disk reads and writes during query execution</li> </ul> <h4 id="example-future-profile-output" class="position-relative d-flex align-items-center group"> Example Future 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="example-future-profile-output" aria-haspopup="dialog" aria-label="Share link: Example Future PROFILE Output"> Share link </button> </h4><div class="highlight"><pre tabindex="0" class="chroma"><code class="language-fallback" data-lang="fallback">| operator | rows | time_ms | memory_kb | |-----------------------|-------|---------|-----------| | NodeScan | 1000 | 5 | 120 | | Filter | 500 | 2 | 80 | | ExpandRelationships | 2000 | 15 | 300 | | Project | 2000 | 1 | 50 | | Sort | 2000 | 10 | 400 | | Limit | 100 | 0 | 10 | | **TOTAL** | 100 | 33 | 960 | </code></pre></div><hr> <h3 id="troubleshooting" class="position-relative d-flex align-items-center group"> Troubleshooting <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="troubleshooting" aria-haspopup="dialog" aria-label="Share link: Troubleshooting"> Share link </button> </h3> <h4 id="explain-returns-empty-plan" class="position-relative d-flex align-items-center group"> EXPLAIN Returns Empty Plan <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="explain-returns-empty-plan" aria-haspopup="dialog" aria-label="Share link: EXPLAIN Returns Empty Plan"> Share link </button> </h4>Problem: EXPLAIN shows minimal or unexpected output. Solutions: <ul> <li>Verify the query syntax is correct (EXPLAIN won’t show errors, it analyzes the parsed AST)</li> <li>Check that the statement type is supported (some statements may show <code>ExecuteStatement</code>)</li> <li>Ensure the query is not too complex (deeply nested queries may show simplified plans)</li> </ul> <h4 id="profile-shows-zero-rows" class="position-relative d-flex align-items-center group"> PROFILE Shows Zero Rows <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-shows-zero-rows" aria-haspopup="dialog" aria-label="Share link: PROFILE Shows Zero Rows"> Share link </button> </h4>Problem: PROFILE returns <code>rows_returned: 0</code> when you expect results. Solutions: <ul> <li>Verify the query would actually return results (run it normally without PROFILE)</li> <li>Check WHERE clause conditions are correct</li> <li>Ensure nodes/relationships exist in the database</li> <li>Verify label names and property keys are spelled correctly</li> </ul> <h4 id="execution-time-always-shows-1ms" class="position-relative d-flex align-items-center group"> Execution Time Always Shows 1ms <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="execution-time-always-shows-1ms" aria-haspopup="dialog" aria-label="Share link: Execution Time Always Shows 1ms"> Share link </button> </h4>Issue: The <code>execution_time_ms</code> metric currently returns a placeholder value (1). Workaround: Use external timing for now: <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash">time geode query "MATCH (p:Person) RETURN count(p)" </code></pre></div>Future: Real timing will be implemented in a future release. <hr> <h3 id="quick-reference" class="position-relative d-flex align-items-center group"> Quick Reference <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="quick-reference" aria-haspopup="dialog" aria-label="Share link: Quick Reference"> Share link </button> </h3> <h4 id="explain-command-1" class="position-relative d-flex align-items-center group"> EXPLAIN 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="explain-command-1" aria-haspopup="dialog" aria-label="Share link: EXPLAIN Command"> Share link </button> </h4><table> <thead> <tr> <th>Purpose</th> <th>Show execution plan without running query</th> </tr> </thead> <tbody> <tr> <td>Syntax</td> <td><code>EXPLAIN <statement></code></td> </tr> <tr> <td>Executes Query</td> <td>❌ No</td> </tr> <tr> <td>Returns</td> <td>Execution plan operators</td> </tr> <tr> <td>Use For</td> <td>Understanding query strategy, comparing approaches</td> </tr> </tbody> </table> <h4 id="profile-command-1" class="position-relative d-flex align-items-center group"> 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="profile-command-1" aria-haspopup="dialog" aria-label="Share link: PROFILE Command"> Share link </button> </h4><table> <thead> <tr> <th>Purpose</th> <th>Execute query and return performance metrics</th> </tr> </thead> <tbody> <tr> <td>Syntax</td> <td><code>PROFILE <statement></code></td> </tr> <tr> <td>Executes Query</td> <td>✅ Yes</td> </tr> <tr> <td>Returns</td> <td>Metrics (rows, columns, time)</td> </tr> <tr> <td>Use For</td> <td>Measuring performance, validating optimizations</td> </tr> </tbody> </table> <h4 id="common-operators" class="position-relative d-flex align-items-center group"> Common Operators <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="common-operators" aria-haspopup="dialog" aria-label="Share link: Common Operators"> Share link </button> </h4><ul> <li>NodeScan: Scan nodes in graph</li> <li>ExpandRelationships: Traverse relationships</li> <li>Filter: Apply WHERE predicates</li> <li>Project: Select RETURN columns</li> <li>Sort: Order results</li> <li>Limit: Restrict row count</li> <li>Aggregate: Group and aggregate</li> </ul> <hr> <h3 id="practice-exercises" class="position-relative d-flex align-items-center group"> Practice Exercises <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="practice-exercises" aria-haspopup="dialog" aria-label="Share link: Practice Exercises"> Share link </button> </h3> <h4 id="exercise-1-basic-explain" class="position-relative d-flex align-items-center group"> Exercise 1: Basic EXPLAIN <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="exercise-1-basic-explain" aria-haspopup="dialog" aria-label="Share link: Exercise 1: Basic EXPLAIN"> Share link </button> </h4>Task: Use EXPLAIN to understand how Geode processes a simple query. <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-gql" data-lang="gql">EXPLAIN MATCH (p:Person) WHERE p.age > 25 RETURN p.name, p.email </code></pre></div>Questions: <ol> <li>What operators are used?</li> <li>Where does the <code>Filter</code> operator appear?</li> <li>What does the <code>Project</code> operator select?</li> </ol> <h4 id="exercise-2-profile-comparison" class="position-relative d-flex align-items-center group"> Exercise 2: PROFILE 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="exercise-2-profile-comparison" aria-haspopup="dialog" aria-label="Share link: Exercise 2: PROFILE Comparison"> Share link </button> </h4>Task: Compare performance of two query formulations. Query 1: <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-gql" data-lang="gql">PROFILE MATCH (p:Person) WHERE p.age > 30 RETURN count(p) </code></pre></div>Query 2: <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-gql" data-lang="gql">PROFILE MATCH (p:Person) RETURN count(CASE WHEN p.age > 30 THEN 1 ELSE null END) </code></pre></div>Compare <code>rows_returned</code> and <code>columns</code>. <h4 id="exercise-3-optimization" class="position-relative d-flex align-items-center group"> Exercise 3: Optimization <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="exercise-3-optimization" aria-haspopup="dialog" aria-label="Share link: Exercise 3: Optimization"> Share link </button> </h4>Task: Optimize a query using EXPLAIN and PROFILE. Initial Query: <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-gql" data-lang="gql">MATCH (p:Person)-[:WORKS_FOR]->(c:Company) WHERE c.industry = 'Finance' RETURN p.name, c.name ORDER BY p.name </code></pre></div>Steps: <ol> <li>Use EXPLAIN to see the plan</li> <li>Identify potential improvements (add index on <code>c.industry</code>?)</li> <li>Use PROFILE to measure initial performance</li> <li>Apply optimizations</li> <li>Use PROFILE to measure improved performance</li> </ol> <hr> <h3 id="next-steps" class="position-relative d-flex align-items-center group"> Next 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="next-steps" aria-haspopup="dialog" aria-label="Share link: Next Steps"> Share link </button> </h3><ul> <li><a href="/docs/query/performance-tuning/" >Query Performance Tuning</a> - Detailed optimization strategies</li> <li><a href="/docs/query/indexing-and-optimization/" >Indexing Guide</a> - Create and optimize indexes</li> <li><a href="/docs/gql/guide/" >GQL Query Language</a> - Master GQL syntax</li> <li><a href="/docs/guides/troubleshooting/" >Troubleshooting Guide</a> - Solve common query issues</li> </ul> <hr> <h3 id="related-documentation" class="position-relative d-flex align-items-center group"> Related Documentation <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-documentation" aria-haspopup="dialog" aria-label="Share link: Related Documentation"> Share link </button> </h3><ul> <li><a href="/docs/security/session-management/" >Session Management</a> - Query execution contexts</li> <li><a href="/docs/transactions/overview/" >Transaction Management</a> - ACID guarantees and isolation</li> <li><a href="/docs/gql/conformance-profile/" >GQL Compliance</a> - ISO/IEC 39075:2024 standard support</li> <li><a href="/docs/analytics/graph-algorithms/" >Graph Algorithms</a> - Built-in algorithm performance</li> </ul> <hr> Last Updated: January 24, 2026 Geode Version: v0.2.18+ ISO GQL Conformance Profile: ISO/IEC 39075:2024 compliance (see conformance profile)