Profile query runtime behavior

Name: Profile query runtime behavior
Availability: InStock
Author: FalkorDB

Profile FalkorDB graph queries with GRAPH.PROFILE to expose runtime execution statistics.

22|2|Updated Jan 27, 2026

Search Tags:#performance analysis #graph database #cypher #query profiling #falkordb #runtime metrics

Ready to run

npx skills add https://github.com/FalkorDB/skills --skill profile-query-runtime-behavior

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: Profile query runtime behavior
Source: https://github.com/FalkorDB/skills/tree/main/cypher-skills/profile-query-runtime
Command: npx skills add https://github.com/FalkorDB/skills --skill profile-query-runtime-behavior

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps developers diagnose slow or inefficient FalkorDB queries by revealing detailed runtime statistics that are unavailable from query planning alone.

Core Features & Use Cases

Runtime Profiling: Execute GRAPH.PROFILE queries to view per-operator execution metrics, record counts, and timing information.
Performance Analysis: Identify expensive query operations and understand where optimization efforts should be focused.
Use Case: When a FalkorDB graph query becomes slow, use this Skill to inspect actual execution behavior and find the operators causing bottlenecks.

Quick Start

Use the profile query runtime behavior skill to analyze the execution performance of my FalkorDB query and identify slow operators.

Frequently Asked Questions about Profile query runtime behavior

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I find slow operators in a FalkorDB Cypher query?▼

To find slow operators in a FalkorDB Cypher query, use GRAPH.PROFILE to execute the query and collect per-operator runtime metrics, exposing execution statistics and record processing counts that pinpoint expensive operations.

What does query profiling show in a graph database?▼

Query profiling in a graph database shows actual runtime execution statistics, including operator timing and record counts, revealing performance bottlenecks that query planning alone cannot expose.

When do I need runtime metrics instead of query plans for Cypher execution analysis?▼

You need runtime metrics for Cypher execution analysis when diagnosing slow queries, because actual execution behavior from GRAPH.PROFILE reveals real timing and record processing bottlenecks unavailable from query plans.

Can I inspect record processing counts for FalkorDB graph queries?▼

Yes, you can inspect record processing counts for FalkorDB graph queries by running GRAPH.PROFILE, which outputs per-operator execution metrics and timing information for diagnosing expensive operations.

What is the best way to diagnose expensive operations in FalkorDB?▼

The best way to diagnose expensive operations in FalkorDB is executing GRAPH.PROFILE to collect actual query metrics, exposing per-operator timing and record counts to identify where optimization efforts should focus.